Re:Declarative Shadow DOM
by chrismorgan on Saturday October 03, 2020 @02:07AM
(#24669943)
A 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.
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.