You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I verified that this issue is not a duplicate. (Search here to find out.)
I did not remove any of the default filter lists, or I have verified that the issue was not caused by removing any of the default lists.
I did not enable additional filter lists, or I have verified that the issue still occurs without enabling additional filter lists.
I do not have custom filters/rules, or I have verified that the issue still occurs without custom filters/rules.
I am not using uBlock Origin (uBO) along with other content blocker extensions.
I have verified that the web browser's built-in blocker or DNS blocking (standalone or through a VPN) is not causing the issue.
I did not answer truthfully to ALL the above checkpoints.
URL(s) where the issue occurs.
https://twitter.com/
Description
Twitter experiments with ads that do not show "Ad" at the top nor have the same tracking divs as seen in the #20792 fix.
From what I've noticed this requires looking in the TweetDetail graphQL, which might not be in scope for this. However having this issue open can hopefully get others to find suitable ways to block purely from something special in the HTML.
Other extensions used
none
Screenshot(s)
Screenshot(s)
Configuration
Details
The text was updated successfully, but these errors were encountered:
Prerequisites
URL(s) where the issue occurs.
https://twitter.com/
Description
Twitter experiments with ads that do not show "Ad" at the top nor have the same tracking divs as seen in the #20792 fix.
From what I've noticed this requires looking in the
TweetDetail
graphQL, which might not be in scope for this. However having this issue open can hopefully get others to find suitable ways to block purely from something special in the HTML.Other extensions used
none
Screenshot(s)
Screenshot(s)
Configuration
Details
The text was updated successfully, but these errors were encountered: