-
-
Notifications
You must be signed in to change notification settings - Fork 232
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
SAXParser: an HTML content inside <noscript> tag is not parsed correctly #105
Comments
parse5 always behaves as an interactive user agent, so it parses noscript as a text, like browsers with enabled javascript do. If you wish to contribute, we can introduce option to switch parse5 to non-interactive user agent mode. Searching Tree Construction section of the HTML spec for "interactive user agent" is a good starting point. |
As I remember browsers with enabled javascript just skip the content of tag Why do not parse a content as HTML in case of HTML by default? :) |
Because it's per spec. |
It's considered as a text. It's just not rendered |
Hi, here is the minimal test case:
The parser supposes that the content of
<nonscript>
is a simple text, but it is an HTML, isn't it?The text was updated successfully, but these errors were encountered: