1.02 KB, text/xul
659 bytes, text/plain
659 bytes, text/html
590 bytes, patch
|Details | Diff | Splinter Review|
createContextualFragment properly parses an <OBJECT> element fragment into an HTMLObjectElement object. If the <OBJECT> element contains a nested HTML comment, then the entire <OBJECT> element is parsed into a Comment object instead. e.g. this: <OBJECT CLASSID="foo"> <!-- Nested comment is here --> </OBJECT> parses as a Comment, while this: <OBJECT CLASSID="foo"> </OBJECT> parses as an HTMLObjectElement. Load the attached test case (commentfrag.xul), when it loads it dumps this to the console: element 1 is: <OBJECT CLASSID="foo"> <!-- Nested comment is here --> </OBJECT> element 1 parses as [object Comment] element 2 is: <OBJECT CLASSID="foo"> </OBJECT> element 2 parses as [object HTMLObjectElement] Both elements should parse as an HTMLObjectElement. Mozilla Build ID: 2000062720
What happens here is that the parser reorders the data and puts the comment in front of the object tag in stead of inside the object tag, I think this is wrong since comments are allowed anywhere in HTML, right? Over to the parser people for futher investigation (load the last testcase in viewer and do a dump content to see what happened)...
Assignee: jst → harishd
Status: UNCONFIRMED → NEW
Ever confirmed: true
This might happen quite frequently. Putting on beta3 radar.
Summary: createContextualFragment incorrectly parses <OBJECT> element with nested comment → createContextualFragment incorrectly parses <OBJECT> element with nested comment
Whiteboard: Fix in hand → [nsbeta3+][Fix in hand]
Fix is in.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
Mass update of qa contact
QA Contact: gerardok → janc
Works for Me Platform: PC OS: Windows 98 Mozilla Version: 2000100508 Marking as Verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.