Re:Inkscape 1.0 Beta 1
by michaelmrose on Wednesday September 18, 2019 @02:24PM
(#21008387)
I mean any reason to believe Mozilla will be out of the running in a few years.
Ah, then you should have replied to the parent!
But no, I personally don't think so - provided web developers do their job and stop designing for one browser. I've been impressed with their recent work - Quantum, developer edition, WebRender etc. Don't care so much for the sync/VPN/other external services, though Firefox Send is quite neat.
- PNaCl, which was essentially Chrome's ActiveX. Thankfully going away in the near future, after nobody else implemented it. See https://www.cnet.com/news/mozilla-coder-chrome-violates-goog...
- The severe limits applied to the webRequest extension API, breaking extensions such as uBlock Origin, without cross-browser consensus: https://blog.mozilla.org/addons/2019/09/03/mozillas-manifest...
- General implementation of new technologies in the browser, without a proper spec/consensus. See <portal>, which has introduced tangible security vulnerabilities into the browser: https://research.securitum.com/security-analysis-of-portal-e...
- Signed HTTP Exchanges and AMP. The controversy around these two has already been well-documented.
- Poorly thought out plans to roll-out default SameSite behaviour whilst a glaring bug was present in Safari which would be exacerbated by the behaviour change (requiring SameSite=None). I'm all for preventing CSRF by default, but these sort of changes should be planned and implemented considerately. See https://news.ycombinator.com/item?id=20905396
- Poor implementation of CT reporting which sent spurious reports to sysadmins even after the policy was supposed to have expired. See https://crbug.com/786563