Closed
Bug 215117
Opened 22 years ago
Closed 22 years ago
SetRootContent handling in nsXMLContentSink is rotten
Categories
(Core :: XSLT, defect)
Core
XSLT
Tracking
()
RESOLVED
FIXED
People
(Reporter: axel, Assigned: peterv)
Details
Attachments
(1 file)
|
1.56 KB,
patch
|
axel
:
review+
jst
:
superreview+
|
Details | Diff | Splinter Review |
There are quite a few special quirks in nsXMLContentSink.cpp when setting the
root content of the nsXMLDocument.
AFAICT, those are from back in the days when XSLT transformed into that same
document. Now, that we don't do things like that anymore, we should set the
root content allright.
The root of evil seems to be
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/content/xml/document/src/nsXMLContentSink.cpp&rev=HEAD&root=/cvsroot&mark=1752#1749
This stuff not only smells funny, but horks document order or top level comments
and PIs with respect to other nodes, ie the document element is hardcoded to
be the last child.
| Assignee | ||
Comment 1•22 years ago
|
||
| Assignee | ||
Updated•22 years ago
|
Attachment #129224 -
Flags: superreview?(jst)
Attachment #129224 -
Flags: review?(axel)
| Reporter | ||
Comment 2•22 years ago
|
||
Comment on attachment 129224 [details] [diff] [review]
One SetRootContent call should be enough
that's what I thought.
Attachment #129224 -
Flags: review?(axel) → review+
Comment 3•22 years ago
|
||
Comment on attachment 129224 [details] [diff] [review]
One SetRootContent call should be enough
sr=jst
Attachment #129224 -
Flags: superreview?(jst) → superreview+
| Assignee | ||
Comment 4•22 years ago
|
||
Checked in.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•