3 ms·
is= is dead, and Safari had good reasons for it. On mobile, so can't quickly find the rationale. But it's the same rationale IIRC why built-in components are n
by dmitriid 5y ago
is= is dead, and Safari had good reasons for it. On mobile, so can't quickly find the rationale.
But it's the same rationale IIRC why built-in components are not extensible (even if this was one of the original promises): the browser has no way of knowing about the actual behavior of the object, which leads to all kinds of mess inside the engine.
- krono 5y agoSo many other parts had to be done in a specific manner or left out entirely to get committee consensus, yet this was written into the spec even though Apple has opposed it from the beginning. The validity of Apple's reasoning makes it even stranger.
- dmitriid 5y agoYeah, the whole thing about Web Components is weird. And is getting increasingly weirder. Quite recently Constructible Stylesheets were released in Chrome: - because lit wanted them - despite Firefox and Safari being against the state of the spec - despite Safari clearly stating they are not going to implement the spec, ever (there was a trivially reproducible race condition in the spec) The entire discussion here: https://github.com/WICG/construct-stylesheets/issues/45#issuecomment-521096423 https://github.com/WICG/construct-stylesheets/issues/45#issu...