Contact emails ansol...@microsoft.com<mailto:ansol...@microsoft.com>, shih...@microsoft.com<mailto:shih...@microsoft.com>
Explainer https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ElementInternalsType/explainer.md Specification None Design docs https://docs.google.com/document/d/1mEAHpBRvqWGxorJB_PIG346gc4U3I5A5SL3q9vYImxc/edit?usp=sharing Summary elementInternals.type supports the creation of custom elements that inherit the behaviors and properties of native HTML elements. When elementInternals.type is set to string values that represent native element types, custom elements can leverage the built-in functionality of standard elements while extending their capabilities to meet specific needs. Blink component Blink>DOM<https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EDOM%22> Motivation Web component authors often want to create custom elements that inherit the behaviors and properties of native HTML elements. By customizing built-in elements, custom elements can leverage the built-in functionality of standard elements and extend their capabilities to meet specific needs. While this can be partially achieved by using 'extends' and 'is', they are not on a path to full interoperability due to their limitations, such as the inability to attach shadow trees to most customized built-in elements. Initial public proposal https://github.com/whatwg/html/issues/11061 Search tags web components<https://chromestatus.com/features#tags:web%20components>, custom elements<https://chromestatus.com/features#tags:custom%20elements> TAG review None TAG review status Pending Risks Interoperability and Compatibility Interop: The WHATWG reached a resolution to accept elementInternals.type = 'button' in https://github.com/openui/open-ui/issues/1088#issuecomment-2372520455. Compatibility: extends/is customized built-ins will not be deprecated. Gecko: No signal (https://github.com/mozilla/standards-positions/issues/1250) No official signal yet, but no objections shared in https://github.com/openui/open-ui/issues/1088#issuecomment-2372520455 WebKit: No signal (https://github.com/WebKit/standards-positions/issues/513) No official signal yet, positive reception shared in https://github.com/openui/open-ui/issues/1088#issuecomment-2372520455 Web developers: Positive (https://github.com/WICG/webcomponents/issues/814) Web developers want interoperable customized built-ins. Link shows support for an alternative to implement a submit button. Other signals: WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? No risks. This feature does not deprecate nor changes the behavior of existing APIs. Debuggability No specific DevTools changes are required. Is this feature fully tested by web-platform-tests<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>? No, Flag name on about://flags Not currently tested, but tests will be added as part of feature development. Finch feature name Pending Non-finch justification A flag will be added as part of feature development. Requires code in //chrome? False Tracking bug https://issues.chromium.org/issues/422947646 Estimated milestones No milestones specified Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5111079237320704?gate=5098147896098816 This intent message was generated by Chrome Platform Status<https://chromestatus.com/>. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/BY1PR00MB2243D1731F212B0D2DC61958FD72A%40BY1PR00MB2243.namprd00.prod.outlook.com.
