You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WebComponents regularly show up as important to developers in surveys like the 2023 state of HTML survey where 42.9% of respondents had used WebComponents, or this MDN APIs & JavaScript survey where WebComponents were ranked as the top feature needing improvement.
Many blog posts and articles have been written in favor of cusomized bultins. A few examples:
I thought we reached somewhat of a consensus at TPAC 2023 to work on custom attributes instead, since they would be able to do more than customized built-ins, without the issues that WebKit had raised.
Description
Customized builtins allow developers to create customized elements that extend the behavior of native HTML elements.
https://html.spec.whatwg.org/multipage/custom-elements.html#custom-elements-customized-builtin-example
They are implemented in Blink and Gecko but not WebKit.
Tests:
https://wpt.fyi/results/custom-elements/builtin-coverage.html
https://wpt.fyi/results/custom-elements/customized-built-in-constructor-exceptions.html
https://wpt.fyi/results/custom-elements/parser
https://wpt.fyi/results/custom-elements/reactions/customized-builtins
Specification
https://html.spec.whatwg.org/multipage/custom-elements.html#customized-built-in-element
Additional Signals
The text was updated successfully, but these errors were encountered: