4 ms·
I’ve just done a bit of investigation on the status of this in browsers. This is what I believe to be the case: • Chrome is roughly planning to ship this in M8
by chrismorgan 6y ago
I’ve just done a bit of investigation on the status of this in browsers. This is what I believe to be the case:
• Chrome is roughly planning to ship this in M88 (Q1 2021).
• There are no signals from Firefox or Safari, positive or negative.
• There were concerns earlier on from various spec and browser developers, but those seem to have generally been sorted out. But https://github.com/mozilla/standards-positions/issues/335 https://github.com/mozilla/standards-positions/issues/335 is still open and awaiting a response.
• As far as putting things into the WHATWG DOM and HTML specs is concerned, at least two implementers must be interested, so it won’t be being landed there just yet.
I invite corrections if I’ve missed anything or erred.
- DaiPlusPlus 6y ago> at least two implementers must be interested Are Chromium-based implementations considered independent implementations if they were developed independently? Like, if both Microsoft and Google work on it for Chromium in secret...
- olliej 6y agono, because that would have meant that IE6 would have been able to "standardize" anything due to the number of "browsers" that were ie wrappers. Alternatively you could look at the numerous browsers on osx and iOS that are essentially wrappers for a basic [NS|WK]WebView - that would allow any of those to count as an alternate implementation.
- thayne 6y agoSo if Mozilla decides maintaining gecko isn't worth it, and switches to blink too, then it's basically just Safari and Chrome, and both would have to agree on standardization?
- deleted 6y ago[deleted]
- olliej 6y agoIt’s kind of already the case. Functionally mobile safari is the only thing stopping google having complete control of the web platform, just as MS did in the days of IE4-6. There are a bunch of standards that google has proposed that are horrific for user privacy, and I would fully expect all google properties to become dependent on them if they didn’t have to care about mobile safari.
- DaiPlusPlus 6y agoI think it's worth distinguishing between "shell" browsers that simply wrap an encapsulated rendering engine (such as those IE6/MSHTML-based browsers from decades ago) and other browsers like Chromium/Edge/Opera which have a different level of integration with the rendering engine - because those browsers are able to tweak and extend - or disable - the engine's features on a granular scale. It's better to compare Chrome/Edge/Opera as "distributions and customizations" of Chromium/Blink instead of mere as wrappers - the same way that Linux distributions aren't reduced to just "GNU/Linux kernel wrappers".
- olliej 6y agoNo, from the point of view of the engine there is no meaningful difference between the engines. Maybe they change some of the defaults, but none of those various wrappers are shipping engines that are different.
- SimeVidas 6y agoThat’s not how open-source collaboration works. If it’s a web platform feature (like in this case), development happens in the open. Everything else would be a scandal.
- pjmlp 6y agoThe way things are going if it wasn't for Safari, we would already all be ChromeOS developers anyway.
- untog 6y agoI dunno, if it wasn't for Safari we'd all be Progressive Web App developers, but they're years behind on implementing common sense standards.
- rektide 6y agoAlas Firefox has been rather joining up on the axis of "we refuse to implement basic stuff" bandwagon. Oh and meanwhile Microsoft is doing really good & helpful work to improve the web platform. In seemingly very very altruistic ways. (Which is how I feel Google is 98% of the time operating too!)
- chrismorgan 6y agoA lot of the time Firefox’s reticence to implement things is because they don’t think it’s the right thing to implement. HTML Imports, for example, were something that everyone wanted, but Firefox developers looked carefully at it and pointed out some very serious problems that weren’t immediately obvious, where implementing HTML Imports would cause a lot of trouble down the track, limiting future extension possibilities. So they said, “let’s hold off on this, wait until we get ECMAScript modules and related loading stuff sorted out, then we can look into redesigning this”. They convinced the Chromium developers, and so they steadily removed it before it could grow too many roots to remove. This is quite different from Safari’s implementation lethargy, which is typically just opaque.