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
Hello guys, thank you for such a pretty and efficient tool!
Nevertheless, I found out that the disableBlockingInPage method in PuppeteerBlocker does not disable blocking completely. To be precise, it does not remove the "domcontentloaded" listener set in the enable method of the BlockingContext class.
This leads to styles injection even after blocking disabling. Here is a couple of simple steps to reproduce the issue:
You might notice that the content and the contentWithoutAds both have cosmetic styles injected. However, I expect the content to be not affected by the blocker at all. Is it a bug or a feature? :)
Thanks in advance!
The text was updated successfully, but these errors were encountered:
Good catch! This definitely looks like a bug. Would you be willing to contribute a patch for this issue? I'd gladly review and publish an update of the package.
Hello guys, thank you for such a pretty and efficient tool!
Nevertheless, I found out that the
disableBlockingInPage
method inPuppeteerBlocker
does not disable blocking completely. To be precise, it does not remove the"domcontentloaded"
listener set in theenable
method of theBlockingContext
class.This leads to styles injection even after blocking disabling. Here is a couple of simple steps to reproduce the issue:
You might notice that the
content
and thecontentWithoutAds
both have cosmetic styles injected. However, I expect thecontent
to be not affected by the blocker at all. Is it a bug or a feature? :)Thanks in advance!
The text was updated successfully, but these errors were encountered: