Add explainer for ElementInternals.type #964
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
cc: @alexkeng since I wasn't able to add you directly as a reviewer |
mwjacksonmsft
approved these changes
Feb 14, 2025
chrisdholt
reviewed
Feb 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
elementInternals.typeAPI was initially proposed here: openui/open-ui#1088 (comment) and accepted by the WHATWG at TPAC. This API provides an improvement over the existing solution for customizable built-ins, ie.extends/is, both in terms of interop (support from Safari) and functionality (shadow trees can be attached to customizable built-ins).This PR captures this proposal in explainer form, and supports
button,submit,resetandlabelas type values.