Browser-laptop: investigate anti-ad blocker on washingtonpost.com

Created on 8 Jun 2017  路  10Comments  路  Source: brave/browser-laptop

Anti-ad blocker in place on the Washington Post.
Confirmed on desktop: PC (Win10) and MacOS

Brave version: https://github.com/brave/browser-laptop/commit/75ffa36130b1ad33c6f311e5e16ed7838b0b50a0

Steps to repro:

Workarounds:

  • Disabling scripts in the Shields menu works.
  • Disabling cache in dev tools also works.
featuradblock needs-investigation site-bug stale

All 10 comments

I think this script is responsible for it. Here is a mirror.

I think these rules in uBO filter fixes it (didn't test, maybe not):

washingtonpost.com###bottom-furniture
washingtonpost.com##html:style(height: initial !important; overflow: auto !important;)

+1 from Twitter https://twitter.com/Music_Journeys/status/882112999955320833

Desktop, OS: Windows 8.1

Brave0.17.13
revf7242c7
Muon4.1.7
libchromiumcontent59.0.3071.109
V85.9.211.38
Node.js7.9.0
  • (another) 1 from Twitter: https://twitter.com/arilitan/status/882132990360301568
    Thanks @jspenguin2017! Appreciate the info. :-)

+1
I got anti-ad blocker in this page:

https://www.washingtonpost.com/news/post-nation/wp/2017/08/06/a-cop-stopped-a-car-for-speeding-then-pointed-a-gun-at-a-passenger-for-more-than-9-minutes/
snap170807_195528

Confirmed on desktop: PC (Win10)

I think rules should update. Thx for owner's effort.

This happens even with adblock turned off, once the anti adblock is shown
washington post

@lukemulks here's the error messages on the console.

mux.js:8 [mux] A monitor for `powa-player-bc40bb0e-1e00-11e7-bb59-a74ccaf1d02f` has not been initialized. mux.js:8 [mux] A monitor for `powa-player-bc40bb0e-1e00-11e7-bb59-a74ccaf1d02f` has not been initialized. chartbeat.js:8 Uncaught TypeError: Cannot read property 'type' of undefined at chartbeat.js:8 at q (chartbeat.js:11) at ma (chartbeat.js:8) at xb (chartbeat.js:42) at W.l.B (chartbeat.js:35) at W.l.B (chartbeat.js:49) at chartbeat.js:8 at cb (chartbeat.js:23) at W.T [as constructor] (chartbeat.js:34) at new W (chartbeat.js:48) Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://s.effectivemeasure.net') does not match the recipient window's origin ('https://www.washingtonpost.com').

You need to allow the 3rd party cookie as well as ads/trackers and reload the page to prevent that from being displayed.

Blocking all cookies works as well. I think it makes impossible to log in to the site, though.

+1 from a macOS user. Will work on resolving. So far, appears only limited to desktop.

Can confirm on desktop site is blocked for brave, even with shields down.

Brave: 0.19.45
rev: cddf9a560535f889201fc0157ebf0b982ea19c00
Muon: 4.4.28
libchromiumcontent: 61.0.3163.100
V8: 6.1.534.41
Node.js: 7.9.0
Update Channel: Beta
OS Platform: macOS
OS Release: 17.2.0
OS Architecture: x64

Hey!!! Adblocking has been growing and growing, showing no signs of letting down. As a publisher, I also face adblocking issues. It intrrupts my ads to load safely on sites. Out of your two tactics, Blockadblock seems effective. Until now, I have used Adzsafe that disables adblockers instantly from user's browser and supports ads to load safely. But I would definitely try this. Thanks!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

lukemulks picture lukemulks  路  3Comments

jonathansampson picture jonathansampson  路  3Comments

antiroyalty picture antiroyalty  路  3Comments

octohedron picture octohedron  路  3Comments

briannyeko picture briannyeko  路  3Comments