3 ms·
I'm not close enough to divine the details, but I'm talking about Chrome plugins not being able to block requests. This might appear to be a facility to protect
by rhizome 14y ago
I'm not close enough to divine the details, but I'm talking about Chrome plugins not being able to block requests. This might appear to be a facility to protect advertising vectors, but I don't know for sure.
http://superuser.com/questions/257102/why-doesnt-chromes-adblock-extension-work-as-well-as-the-one-in-firefox http://superuser.com/questions/257102/why-doesnt-chromes-adb...
- Spittie 14y agoThis used to be true, not thing have changed since then. Chrome didn't have any WebRequest api, so Adblock Plus for Chrome loaded some JS/CSS in the page and tried to hide/block as much ads as possible. [1] Since Chrome 14 (i'm not totally sure about this version) WebRequest api where implemented, but only as experimental api (you would have to enable them from chrome://flags), and Chrome >17 enable them by default. So Adblock Plus >1.2 beta [2] and Chrome >17 should block ads just like Firefox. It's possible that there are some small difference, but that's likely a bug and should be reported. [1] http://adblockplus.org/development-builds/experimental-adblock-plus-for-chrome-builds-available-with-better-blocking http://adblockplus.org/development-builds/experimental-adblo... [2] http://adblockplus.org/releases/adblock-plus-12-beta-for-google-chrome-released http://adblockplus.org/releases/adblock-plus-12-beta-for-goo... I'm not sure what's the situation with other adblocker for chrome.