Uassets: Washington post anti-adblock.

Created on 24 Sep 2019  路  23Comments  路  Source: uBlockOrigin/uAssets

URL(s) where the issue occurs

https://www.washingtonpost.com/nation/2019/03/29/decades-garfield-telephones-kept-washing-ashore-france-now-mystery-has-been-solved/

Describe the issue

Anti-Adblock popup is still appearing on Washington Post

Screenshot(s)

image

Versions

  • Browser/version: Firefox 70 Beta
  • uBlock Origin version: 1.22.2

Settings

  • All Filters Enabled. Advanced User Enabled.

Notes

The adblock popup is identical to #6280. I am still seeing it despite updating all filters.

external unable to reproduce

All 23 comments

I can't reproduce with a default setup using Chromium or Firefox.

@Marsfan

washingtonpost.com##[class] > div:has-text(blocking ads)
washingtonpost.com##html:style(overflow: auto !important)

You can try those.

No recover right column:

pic

|
---|

I've been having the same issue over the past 4 or 5 days. It occurs randomly and I can mitigate it by refreshing the page 2 or 3 times.

I created a filter @@||washingtonpost.com^$generichide which did not make any difference. I also tried disabling cosmetic filtering on the site, which also made no difference.

I use default uBO filters with the addition of Fanboy's Enhanced Tracking List and the anti-blocker list from https://github.com/bogachenko/fuckfuckadblock. I use Firefox 69.0.1 portable 64-bit on Windows 10 Home 64, build 1809, uBO 1.22.2

I've been having the same issue over the past 4 or 5 days. It occurs randomly and I can mitigate it by refreshing the page 2 or 3 times.

Race condition is affecting you then.

@VernonStow Add the filters I posted -- https://github.com/uBlockOrigin/uAssets/issues/6339#issuecomment-534698785

There should not be any race condition problem using Firefox because we are using
washingtonpost.com##^script:has-text(("0x)

@VernonStow can you see that filter in the logger?
image

If you can see it and still get the anti-adblock message do you have the Firefox tracking protection enabled and what other extensions do you use?

There should not be any race condition problem using Firefox because we are using
washingtonpost.com##^script:has-text(("0x)

@VernonStow can you see that filter in the logger?
image

If you can see it and still get the anti-adblock message do you have the Firefox tracking protection enabled and what other extensions do you use?

I do see the filter. I left "tracking protection" on for WaPo (although I find I have to disable it at most websites that display charts and graphs). I also use the paywall add-on at https://github.com/iamadamdev/bypass-paywalls-firefox, although when I toggled it on and off yesterday and refreshed the page several times, I couldn't get WaPo to display the adblock warning.

if you still see the anti adb stuff, try:
washingtonpost.com##+js(raf-if, !jQuery.fx.tick)

I just got a screen grab from it with the new filter added and "tracking protection" turned off. https://www.washingtonpost.com/opinions/impeachment-will-define-the-2020-election/2019/09/25/7b931390-df82-11e9-be96-6adb81821e90_story.html

WAPO 1
WAPO 2

I don't see
washingtonpost.com##^script:has-text(("0x)

I didn't see it listed under Blocked or Allowed, although I had added it to my filters.

You should disable bypass-paywalls, keep tracking protection OFF, reopen FF and test again.

or
as above but reset uBo to default settings, update the lists and test again

image
Your link on my end using Firefox. There is no need to add it to my filters it is already part of uBO-filters.

Sorry, I had confused that with the washingtonpost.com##+js(raf-if, !jQuery.fx.tick) filter.

No problem, washingtonpost.com##^script:has-text(("0x) should work if you use Firefox unless some external extension or Firefox itself get's in the way.
Can you reproduce the anti adblock message if you disable the tracking protection and disable all extensions except uBO?

I have cleared cookies and disabled tracking protection and the paywall add-on, and cannot get the anti-adblock page to reappear after opening and refreshing 12 article links. I can see the washingtonpost.com##^script:has-text(("0x) filter as the first item blocked on each page. It would appear that the paywall add-on is interfering with uBO.

Thanks for testing.

Glad to be of help.

I can reproduce anti-adb sometimes with this article in Chrome with only uBO installed with default filters.

Cosmetic filters with extended syntax appear to work on my end to solve this, can someone else who is seeing the notice test the following filters work to remove the overlay notice and add the page scrollbar back?

wapo

wapo2

washingtonpost.com##div:has-text(We noticed you鈥檙e blocking ads.)
washingtonpost.com##.db-ns[style="height: 1250px;"]
washingtonpost.com##html[style="overflow: hidden;"]:style(overflow: auto !important;)

They will because the ones I posted are similar to yours, https://github.com/uBlockOrigin/uAssets/issues/6339#issuecomment-534698785

They will because the ones I posted are similar to yours, #6339 (comment)

Missed that somehow - thanks

No recover right column:

@krystian3w washingtonpost.com##.db-ns[style="height: 1250px;"] work?

I can reproduce anti-adb sometimes with this article in Chrome

A race condition is possible using Chromium/Chrome, though I can't reproduce,

Was this page helpful?
0 / 5 - 0 ratings

Related issues

wis picture wis  路  4Comments

Jose1971AB picture Jose1971AB  路  3Comments

macheteBadger picture macheteBadger  路  3Comments

Jose1971AB picture Jose1971AB  路  3Comments

terrorist96 picture terrorist96  路  3Comments