News for hackers. Stuff that matters.
Re:Firefox 15 plugs the add-on leaks by rhizome on Thursday July 19, 2012 @01:48PM (#4267184)
AdBlock sucks on Chrome due to Google's architecture choices.
Re:Firefox 15 plugs the add-on leaks by cpeterso on Thursday July 19, 2012 @06:05PM (#4268312)
Architecture choices or business model?
Re:Firefox 15 plugs the add-on leaks by rhizome on Thursday July 19, 2012 @06:24PM (#4268378)
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-adb...

Re:Firefox 15 plugs the add-on leaks by Spittie on Thursday July 19, 2012 @09:23PM (#4268918)
This 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-adblo...

[2] http://adblockplus.org/releases/adblock-plus-12-beta-for-goo...

I'm not sure what's the situation with other adblocker for chrome.