I suspect this is partly why Firefox is losing the battle. By concentrating resources on nice-to-have user functionality rather than implementing core technologies that web developers actually build sites with, we end up with more and more websites that only work in Chrome. Far fewer users care about browser config than "does my internet banking site work?". Firefox probably needs to work on that, even if it means making the browser work with Chrome's non-standard implementations of things, to retain users.
I suspect that would be easier than persuading web developers to target more browsers unfortunately.
Re:The Firefox Dilemma
by chupasaurus on Tuesday December 11, 2018 @06:01AM
(#18654511)
> rather than implementing core technologies that web developers actually build sites with
Like a Shadowdom API v0 (v1 is standartized by W3C) used by Google in Polyfill so Youtube is way slower?
> even if it means making the browser work with Chrome's non-standard implementations of things
How good the compatibility between Internet Exploder's features and FF/Chrome was?
Re:The Firefox Dilemma
by olejorgenb on Tuesday December 11, 2018 @06:16AM
(#18654572)
Yes, I use Firefox for browsing, but Chrome for developing.
I should probably give Firefox's tools another chance, but last time I checked Chrome's dev tools was alot better.
Chrome simply isn't configurable enough to make it nice to use for me.