Should "script supporting elements" read "script and template"? #467
Unanswered
estelle
asked this question in
Browser compatibility data
Replies: 1 comment 2 replies
-
Thanks @estelle - is the in-page suggestion to add it to the 'Technical Summary' table as per the linked pr? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Most non-empty elements support script-supporting elements (script and template), so we should either include it on all the elements that do (body, ol, li, hgroup, h1-h6, etc), or create a page for script supporting elements similar to global attributes (which are global to all element, not just "not empty" elements), and then refer to it as we refer to the page that explains script and template being able to be nested almost anywhere.
According to the spec, the following are explicitly listed as including script supporting elements in their content model:
(this does not include elements that include them indirectly in "phrasing content").
This isn't a large list.
We can include this just on these elements (Will's preference)
Alternatively, since they are supported everywhere, we could make it global, with the empty element caveat (Estelle's preference)
(Converstation originally between @estelle and @wbamberg in mdn/content#29827)
Beta Was this translation helpful? Give feedback.
All reactions