There's definitely a PR manager in Chrome who gets a bonus every time this line is repeated. > and you can draw a straight line from Apple’s overwhelming institutional arrogance to Safari being the “new IE”.

I would also recommend you read this comment on the whole process and 'obligation to implement' and other things (it's not from Apple). The fact of matter is, we only agreed to keep it in the spec to wait until the feature becomes at-risk at CR stage so that it can be removed. The thing is, Apple has been objecting to this feature from the get go, and the only reason it remains in the spec is because Google kept objecting to it being removed from the spec. See, for example, Template Instantiation Proposal (among many other things). So did Safari endorse Web Components? Yes. Extension of builtin elements are much better served with mixins. HTMLInputElement, etc.) for various reasons, so WebKit isn't going to support this feature anyway. We're against subclassing subclasses of HTMLElement (e.g. We extremely reluctantly agreed to keep it in the spec until it gets removed at risk later. I'll note that we've vocally and repeatedly objected to having is=, and in fact, stated publicly that we won't implement this feature, but somehow the WG kept it in the spec. Now I'm going to re-iterate that Apple objects to extending subclasses of HTMLElement using is= as currently spec'ed for various reasons we've stated in the past and this feature won't be supported in WebKit. Let's see about that endorsement and 'undermining': > Endorsing a standard, then undermining it This also means that none of the browser implementors should be on the steering committee by your criteria. > Members of a standards body are accountable for their actions. So something tells me it's there only because of the planned removal of the built-in alert/confirm/prompt, and not for any other reason. None of the decade-long issues with dialog have been fixed, including these accessibility issues Safari (and Mozilla) have had no interest in implementing this element as it's currently specced Safari (and Mozilla) have been opposed to the current state of the spec for 10 years now

Skip to Safari 15, and we're suddenly getting even though: Chrome was just the first.Īnd yet there's literally no replacement for those. It looks like browser implementors agreed to remove those from all three browsers. įast forward to 2021, and Chrome breaks the web by removing built-in alert/prompt/confirm dialogs: Now the same very people, including Domenic, were arguing that alert is bad for security, bad for the Javascript engine etc. In 2018 Domenic Denicola mentioned that it's possible dialog should be fully removed as there's no interest in implementing it. And this was one of the many reasons why neither Safari nor Firefox implemented.

Experimental webkit features