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.

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

Noframes tag not parsed according to specification when in body #972

Closed
leeN opened this issue Jul 3, 2023 · 0 comments · Fixed by #1277
Closed

Noframes tag not parsed according to specification when in body #972

leeN opened this issue Jul 3, 2023 · 0 comments · Fixed by #1277

Comments

@leeN
Copy link

leeN commented Jul 3, 2023

Hello,

I found that parse5 does not adhere to the HTML specification when it comes to parsing the noframes tag outside of the head of a document.

According to the specification, when a noframes tag is encountered inside a document's body, it should be processed as if it was in head, i.e., with raw text content. Parse5 however seems to parse it as if it were a custom tag. For the other tags listed in the spec it behaves correctly, but noframes seems to be missing here

Example:

<r><noframes><math id="</noframes><b>should be outside of noframes</b>">

Explorer link.

In head mode the content of noframes should be parsed as raw text, that is the closing tag inside the id attribute of the math tag should close the opening noframes tag and the following b tag should be outside of noframes.

nolanlawson added a commit to nolanlawson/parse5 that referenced this issue Sep 30, 2024
43081j pushed a commit that referenced this issue Oct 6, 2024
* fix: fix `<noframes>` parsing

Fixes #972
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant