The ad-block feature stopped working with Chrome / chromedriver 133 #3504
Labels
bug
Uh oh... Something needs to be fixed
workaround exists
You can reach your destination if you do this...
The ad-block feature stopped working with Chrome / chromedriver 133
This is a feature activated via:
ad_block=True
/--ad-block
. It stopped working recently because Chrome / chromedriver 133 has dropped support for Manifest-V2 extensions. (People have to use Manifest-V3 extensions now.)The temporary workaround is to set
driver_version=132
/--driver-version=132
.The permanent workaround likely involves implementing something like https://www.youtube.com/watch?v=H3vFL_O_0Lo ("Build an AD BLOCKER Chrome Extension in Less Than 10 Minutes")
Even Google can agree that clicking on ads via automation is not good (click-fraud), so it's in everyone's best interests to get a new ad-blocker working in Manifest V3 for SeleniumBase so that automated scripts don't accidentally click on ads. (It's not likely that automation would click those deliberately, unless people specify the wrong selectors or too-broad ones such as "iframe".)
The text was updated successfully, but these errors were encountered: