And the other point of view: > We're certainly aware of how significant ad block...

zamalek · on July 9, 2019

> FUD

I originally commented there and expressed how they were underestimating the importance of ad blocking. One of the issues I pointed to as evidence (https://github.com/mozilla-mobile/fenix/issues/96) has since been re-prioritized to Q3.

They seem to have heard the message.

JeremyNT · on July 9, 2019

> This reads like FUD to me. The dev team know how important extensions are to their users.

Just because they know how important it is doesn't mean they care.

I'm sure Google also knew how important ad blocking was to many Chrome users when they decided to remove that functionality from their browser, too.

BiosElement · on July 9, 2019

uBlock seems to work just fine, not sure why you're claiming they removed it.

wtallis · on July 9, 2019

He's not claiming that they removed it. He's referring to the fact that Google announced their intention to remove the APIs that uBlock relies on. They haven't followed through with the plan yet, but neither have they completely backtracked. See eg. https://www.androidpolice.com/2019/05/29/google-still-plans-... and reports that they'll continue to provide that functionality only to enterprise users: https://9to5google.com/2019/05/29/chrome-ad-blocking-enterpr...

techntoke · on July 10, 2019

Chrome devs made it clear that just because the API is changing that adblocking will still be supported and it will be faster. Sometimes APIs change.

krageon · on July 10, 2019

The API was crippled, not changed. There is a fairly lengthy explanation of how it is bad and why by the author of uBlock Origin: https://github.com/uBlockOrigin/uBlock-issues/issues/338#iss...

sascha_sl · on July 10, 2019

being able to decide for every request with code vs a limited number of patterns you can pre-populate is not an equally useful API replacement

icebraining · on July 9, 2019

Chrome didn't remove ad-blocking.

kevin_b_er · on July 9, 2019

More "features will land", not necessarily extensions. They have limited internal extensions API because several of their features were implemented with bundled extensions, but it doesn't talk about extensions/addons themselves.

And, yes, there's the "ad blocking" issue: https://github.com/mozilla-mobile/fenix/issues/96

What does it actually say? The requirement is "Integrate/support for different adblock lists (see Focus)".

So you can have certain ad-block lists, but not the actual customization and not uBlock Origin.