Bug 231575
| Summary: | Customized built-in elements | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Stephen Belovarich <steveblue> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Blocker | ||
| Priority: | P2 | ||
| Version: | Safari 15 | ||
| Hardware: | All | ||
| OS: | All | ||
Stephen Belovarich
Web Components are indispensible for user interface development although major portions of the set of specifications that comprise Web Components are missing in WebKit. One specification that should be supported in WebKit is customized built-in elements. Would Apple reconsider their position regarding customized built-in elements given the specification is broadly supported in Chrome, Firefox, and Edge?
As a web developer, omissions from specifications documented in the HTML Living Standard are problematic at best. It makes our jobs difficult having to track the missing features from WebKit. Having to load a polyfill for customized built-in elements in Safari reduces the benefit of custom elements for the end user, because they are expected to be parsed and rendered directly by the browser.
Link to specification: https://html.spec.whatwg.org/multipage/custom-elements.html#custom-elements-customized-builtin-example
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Sam Sneddon [:gsnedders]
*** This bug has been marked as a duplicate of bug 182671 ***