Closed Bug 45566 Opened 21 years ago Closed 9 years ago

DOMParser should throw exceptions for not-well-formed XML


(Core :: XML, enhancement)

Not set





(Reporter: taras.tielkes, Unassigned)




(1 file)

At the moment the the DOMParser component from the xmlextras module doesn't 
report any fatal errors (such as XML that is not well-formed). It appears that 
some error message is included in the (DOM) document tree.

It would be nice if we could catch parser exception using the ECMAScript 
try/catch/finally construct.
Target Milestone: --- → mozilla0.9
I am taking all XMLExtras bugs to make it easier to see what I am working on...
Assignee: vidur → heikki
This is also something that should be replaced with DOM Level 3 Load & Save
module implementation.
Whiteboard: [Replace with DOM 3 Load & Save]
I do not want to change these so close to the milestone deadline. Besides, I
want to replace the DOMParser and XMLSerializer with DOM 3 Load & Save. Moving
to 0.9.1 for now.
Target Milestone: mozilla0.9 → mozilla0.9.1
Target Milestone: mozilla0.9.1 → mozilla0.9.2
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Doesn't look like this is getting fixed before the freeze tomorrow night.
Pushing out a milestone.  Please correct if I'm mistaken.
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Target Milestone: mozilla0.9.4 → mozilla0.9.5
Target Milestone: mozilla0.9.5 → mozilla0.9.6
Target Milestone: mozilla0.9.6 → mozilla0.9.8
Target Milestone: mozilla0.9.8 → mozilla0.9.9
Target Milestone: mozilla0.9.9 → Future
QA Contact: petersen → rakeshmishra
QA Contact: rakeshmishra → ashishbhatt
(About DOM LS and error reporting: note bug 155749 comments 26-32.)
Blocks: 340383
This bug is laying dormant for a while... :(
Assignee: hjtoi-bugzilla → nobody
Blocks: 289714
Priority: P3 → --
QA Contact: ashshbhatt → xml
Whiteboard: [Replace with DOM 3 Load & Save]
Target Milestone: Future → ---
heh, an open bug for 10 years... :)

and it just bit me... :(
Invalid per spec: <> and Opera reports this would be web-incompatible.
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.