Open
Bug 231798
Opened 21 years ago
Updated 3 years ago
errors propagate too far during parsing
Categories
(Core :: DOM: Core & HTML, defect, P5)
Core
DOM: Core & HTML
Tracking
()
NEW
People
(Reporter: sicking, Unassigned)
Details
Spinoff from bug 230360
Some of the errors that can happen during parsing end up getting propagated too
far. And some of them should not even be errors in the first place.
One example is NS_ERROR_HTMLPARSER_BLOCK that doesn't indicate that anything has
actually gone wrong, just that the parser needs to be blocked.
Another example is that during CloseElement we will get an error from <link>
elements if the stylesheet can't be loaded. However the reason could be as
simple as stylesheets being turned off since we're loading a datadocument.
A good place to search is the codepaths called during CreateElement and
CloseElement.
See also bug 230360 comment 6 to 8
Updated•16 years ago
|
Assignee: general → nobody
QA Contact: ian → general
Comment 1•7 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046
Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.
If you have questions, please contact :mdaly.
Priority: -- → P5
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•