Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify context of §4.12.2 the <noscript> element #10159

Open
doriantaylor opened this issue Feb 24, 2024 · 1 comment
Open

Clarify context of §4.12.2 the <noscript> element #10159

doriantaylor opened this issue Feb 24, 2024 · 1 comment

Comments

@doriantaylor
Copy link

What is the issue with the HTML Standard?

Where §4.12.2 reads:

Contexts in which this element can be used:
In a head element of an HTML document, if there are no ancestor noscript elements.
Where phrasing content is expected in HTML documents, if there are no ancestor noscript elements.

Consider adding the following sentence:

Where flow content is expected in HTML documents, if there are no ancestor noscript elements.

Such a change would not only make the spec consistent with itself, but also HTML 4.01 and XHTML 1. See validator/validator#1694 for additional information.
@Kaiido
Copy link
Member

Kaiido commented Feb 25, 2024

I'm not sure to understand. <noscript> is already valid as a child of <body> in an HTML document, (your document is parsed as an XHTML one).
Pardon my possible naivety, but what inconsistency are you referring to? Why should the HTML specs be changed? How would that fix the issue with XML and XHTML?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@doriantaylor @Kaiido