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.
- 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.)