-
Notifications
You must be signed in to change notification settings - Fork 776
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ALL facebook.com issues #3367
Comments
I see nothing Can it be adware? |
No i don't have any adware or some adware extensions, the ads are from Facebook ( sponsored ) |
While on a page with ads, right click on page, save as ..., you'll get a folder + html page, zip them together, upload the zip on some free server. Post here the link. |
Here the page with the sponsored ad: https://ufile.io/y827j |
@GetGankNow test this filter |
@mapx- is blocking all post but allowing the comment section and reaction section. |
|
@mapx- works bro, thanks a lot. |
Edit: some sponsored ads are appearing again. |
another example page ? |
The page that i save include all ads, i don't know how to save the page without the ads of this: facebook.com###substream_1:has([id^="feed_subtitle_"]:has-text(Sp)) |
facebook.zip |
test
|
@mapx- this 3 rules works. Thanks for all!! |
test |
weird, working for me (exactly using your test-case) Did you test the same case you uploaded ? or something new ? could be "they" are using different approaches |
Doesn't work for me either. I had to use something like this:
However, with this filter active, FB seems to be refreshing the posts in an infinite loop. |
From about 3mo to about 2wk ago, it was possible to catch Sponsored posts with :has-text(SpSonSsoSredS). This appeared only in Sponsored posts, with the 'S' elements hidden by CSS. (I'm not sure about back then, but now, the hiding CSS uses 'font-size:0', not 'display:none'.) About 2wk ago, they started putting that stuff into all(*) posts. In Sponsored posts they use CSS to hide the 'S' elements. In 'normal' posts they use CSS to hide all of this. :has-text() is not aware of CSS hiding. The CSS used for this hiding is cryptographically hashed; so far it has remained stable for me, but another user has completely different classes, so the simple selector I use in my own filter won't work for anyone else. So we have to get into runtime evaluation of CSS computed styles :( [(*)Not really 'all', but all normal posts by users, and many Sponsored posts, although some emitted by other modules inside FB don't use this particular trickery.] It seems like uBO :matches-css() [see: https://github.com/gorhill/uBlock/wiki/Procedural-cosmetic-filters] might be able to handle this. Something like:
-- which is COMPLETELY UNTESTED, just a pile of syntax smashed together by hand. Not sure if the nested uBO selectors are supported... And all they need to do to break this is chop the word 'Sponsored' up differently; and it won't work for other UI languages. This is getting ugly. |
Maybe need to view the deep of they DOM tag, e.g. looking in for example, I've found some part of sponsored URLs have |
Hi, I saw the comment in filters so I'd like report here:
Thanks. |
The only way we can investigate properly is you need to reproduce the issue in a new browser profile with only uBO and its default settings first. Then we'll test on that profile. |
Ok, I've took time to test this. It's actually chrome/chromium's issue. With ublock origin even disabled in extension, and all extensions are disabled, open those six tabs chrome (both 128 and 131 version, with preload page off, memory saver on) will go mad. While librewolf (firefox 131) with ublock origin enabled , there's no issue. So it's false alram, its entirely chrome's problem (or my profile). So discard my previous reports. Thanks for the support. |
It appears that sometimes, on the loading of the content, that the Marketplace pages get completely emptied out:
|
URL(s) where the issue occurs
Facebook.com
Describe the issue
The Facebook sponsored ads is appearing again, i have tried all the solutions but nothing works
Versions
Settings
The text was updated successfully, but these errors were encountered: