Open
Bug 717206
Opened 13 years ago
Updated 4 years ago
Remove blocking state from the parsers, ask nsScriptLoader for blocking state
Categories
(Core :: DOM: HTML Parser, enhancement, P5)
Core
DOM: HTML Parser
Tracking
()
NEW
People
(Reporter: hsivonen, Unassigned)
References
Details
Currently, nsScriptLoader maintains the parser-blocking script and parsers have a separate flag that's supposed to keep in sync with the parser-blocking script being null or non-null.
Parsers (or the sink, rather) should probably ask nsScriptLoader for the blockingness state instead of maintaining a copy of the state.
Note: Fragment parsers must not ask the script loader for the blockingness state.
Comment 1•4 years ago
|
||
Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority and severity.
If you have reason to believe this is wrong, please write a comment and ni :jstutte.
Severity: normal → S4
Priority: -- → P5
You need to log in
before you can comment on or make changes to this bug.
Description
•