News for hackers. Stuff that matters.
Re:Manifest v3 in Firefox: Recap and Next Steps by worble on Wednesday May 18, 2022 @05:17PM (#31427799)
The fact that Firefox is standing up to Google and their crippling of WebRequest is a good thing, for users at least.

The alternative is not "unity", it's Google dictating standards that only ostensibly help them and their ad business.

Re:Manifest v3 in Firefox: Recap and Next Steps by sharken on Thursday May 19, 2022 @02:18AM (#31431321)
But what are the options when Google gets to dictate how Chrome and Microsoft Edge behaves.

That is 75% of the browser market, so Google could in theory define their standards and not care about other browsers.

The Ad-friendliness of Googles implementation of Manifest V3 is a clear example of how Google uses their influence.

Somehow the standards commission should have more to say about the process and implementations, i just don't see how.

And it all started out so nice.

https://www.w3.org/community/webextensions/2021/06/04/formin...

Re:Manifest v3 in Firefox: Recap and Next Steps by chii on Thursday May 19, 2022 @05:56AM (#31432593)
> And it all started out so nice.

road to hell is paved with good intentions.

Re:Manifest v3 in Firefox: Recap and Next Steps by pjmlp on Thursday May 19, 2022 @03:21AM (#31431694)
I still use Firefox as my main browser, but lets not fool ourselves, it hardly matters with its current market share.
Re:Manifest v3 in Firefox: Recap and Next Steps by reitanqild on Thursday May 19, 2022 @04:47AM (#31432207)
Actually I feel the pendulum has stopped a few months ago and is slowly starting to go back. Some major things in my world:

- I now only have one website I need to use that only works in Chrome.

- Devs seems to start to care

- LibreWolf is starting to give Mozilla a run for its money

- I'm optimistic that we will see some break through, sooner or later, where Chrome will be punished as hard as IE was: fines, regulations and a browser choice dialog for starters (but please folks, it can happen a lot faster if it it isn't just "that one weird loon", so do contact your local authorities and do complain about how Chrome has destroyed a thriving ecosystem. And if you work in Google, do ask tough questions.)

Re:Manifest v3 in Firefox: Recap and Next Steps by pjmlp on Thursday May 19, 2022 @05:06AM (#31432319)
On my world, Firefox no longer makes part of browser matrixes, and is mostly ignored by QA teams.

If it wasn't for Safari, most Webdevs could update their CV as ChromeOS developer.

Re:Manifest v3 in Firefox: Recap and Next Steps by chii on Thursday May 19, 2022 @05:55AM (#31432584)
> Firefox no longer makes part of browser matrixes, and is mostly ignored by QA teams.

which is how a browser dies - when sites and apps stop checking whether they are complying with web standards using more than a single reference browser.

Hopefully, chrome becomes like the IE of old, and a new "chrome" comes along to rescue the web.

Re:Manifest v3 in Firefox: Recap and Next Steps by pjmlp on Thursday May 19, 2022 @06:07AM (#31432643)
Hence why Safari is the only one holding Chrome back, thanks to iDevices.