Open Bug 1960845 Opened 6 months ago Updated 5 months ago

Investigate the behavior around <noscript> with parseHTML

Categories

(Core :: DOM: Core & HTML, task)

Product:
Core
Component:
DOM: Core & HTML
Type:
task

Tracking

()

People

(Reporter: tschuster, Unassigned)

References

(Blocks 1 open bug)

Details

While implementing parseHTML, I stumbled upon the parameter aScriptingEnabledForNoscriptParsing of nsContentUtils::ParseDocumentHTML.

Setting this boolean results in a parsing difference for the following HTML:

<head><noscript>Hello World</noscript></head>

With false it produces:

<head><noscript></noscript></head><body>Hello World</body>

With true:

<head><noscript>Hello World</noscript></head><body></body>

The already existing parseHTMLUnsafe function also uses false. I feel like the behavior of true makes more sense though? The right behavior is probably implied by something in the specification.

Component: DOM: Security → DOM: Core & HTML
See Also: → 1965760
You need to log in before you can comment on or make changes to this bug.