News for hackers. Stuff that matters.

A comment on Manifest v3 in Firefox: Recap and Next Steps. Parent comment

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.

[ Parent | on HN ]
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.

[ Parent | on HN ]
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.
[ Parent | on HN ]