feat(standards): add html-dom spec #2337
Closed
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.
This table is new and not part of the previous lookup table. It replaces some hardcoded values in our code and allows us to work on #1597 and #601 by allowing us to identify interactive content.
Replaces these values:
phrasingElements
in subtree-texthtmlTags
in is-html-element (which is why there are empty objects)possibleShadowRoots
in is-shadow-root.jssectioningElementSelector
in lookup-table.jsThere might be a few more but those were the ones I could find in a quick element search.
Just like we plan to do for the
aria-attributes
spec, we should create a commons helper that aggregates information from this table into useful forms, such as getting all elements that are of a certain content type.Reviewer checks
Required fields, to be filled out by PR reviewer(s)