Remove categories of select/optgroup/option element inner content elements#12568
Open
dbaron wants to merge 1 commit into
Open
Remove categories of select/optgroup/option element inner content elements#12568dbaron wants to merge 1 commit into
dbaron wants to merge 1 commit into
Conversation
…ments. This removes the categories: * select element inner content elements * optgroup element inner content elements * option element inner content elements in order to simplify the specification a bit. It does so by making the div content model rules that use these concepts instead use the transparent content model concept, which works for these cases and is perhaps also more clear. This is a followup to whatwg#12504 and also has the goal of simplifying the content model changes we will need in whatwg#12011. (I think whatwg#12011 may also need the concept of limiting this transparency to certain close descendants but not all descendants, but I don't think that concept is needed for the select content models.)
mtrootyy
reviewed
Jun 11, 2026
| <dd><span><code>option</code> element inner content elements</span>.</dd> | ||
| <dt><span data-x="concept-element-contexts">Contexts in which this element can be used</span>:</dt> | ||
| <dd>Where <span>flow content</span> is expected.</dd> | ||
| <dd>As a child of a <code>dl</code> element.</dd> |
There was a problem hiding this comment.
Add the following:
As a descendant of an option element, an optgroup element or select element
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 removes the categories:
It does so by making the div content model rules that use these concepts instead use the transparent content model concept, which works for these cases and is perhaps also more clear.
This is a followup to #12504 and also has the goal of simplifying the content model changes we will need in #12011. (I think #12011 may also need the concept of limiting this transparency to certain close descendants but not all descendants, but I don't think that concept is needed for the select content models.)
(See WHATWG Working Mode: Changes for more details.)
(Sorry, I wrote this last week right after landing #12504, but I forgot to actually create the PR!)
/dom.html ( diff )
/form-elements.html ( diff )
/grouping-content.html ( diff )
/index.html ( diff )
/indices.html ( diff )
/scripting.html ( diff )