Clearly, Google is serious about trying to oust ad blockers from its browser, or at least those extensions with fuller (V2) levels of functionality. One of the crucial twists with V3 is that it prevents the use of remotely hosted code – as a security measure – but this also means ad blockers can’t update their filter lists without going through Google’s review process. What does that mean? Way slower updates for said filters, which hampers the ability of the ad-blocking extension to keep up with the necessary changes to stay effective.
(This isn’t just about browsers, either, as the war on advert dodgers extends to YouTube, too, as we’ve seen in recent months).
At any rate, Google is playing with fire here somewhat – or Firefox, perhaps we should say – as this may be the shove some folks need to get them considering another of the best web browsers out there aside from Chrome. Mozilla, the maker of Firefox, has vowed to maintain support for V2 extensions, while introducing support for V3 alongside to give folks a choice (now there’s a radical idea).
When new fearures added to V3, will Mozilla port it to V2 too?
IIRC, they’ve said they’ll implement V3 to maintain compatibility, but they’ll also continue to maintain V2. You, the extension developer, will not be forced to use V3 if you don’t want to.
educated guess: since firefox is implementing v3 support alongside their v2 extensions, there shouldn’t be any issues running v2 and v3 extensions side by side in the foreseeable future
I think they are wondering if one extension can use both v2 and v3 APIs at once? As in whether v3 APIs will be “backported” to allow v2 extensions to use them
I wonder how they’ll solve that riddle.