Closed
Bug 398410
Opened 17 years ago
Closed 17 years ago
crash when using the results of ORDERED_NODE_SNAPSHOT_TYPE
Categories
(Core :: XSLT, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: chris.shoemaker, Assigned: sicking)
References
Details
Attachments
(1 file)
710 bytes,
text/html
|
Details |
I realize that the results of an ORDERED_NODE_SNAPSHOT_TYPE may not remain valid through document mutations. However, this script crashes minefield hard. Perhaps the crash is a separate bug, but my impression is that the snapshot is using a rather fragile way of referencing attribute nodes, e.g. by some index rather than by name. When the first line in crash() is commented out, it no longer crashes, but it still end up removing attributes that don't belong in the snapshot. I don't know the spec well enough to assert that this is a violation, but it certainly feels like it defeats the entire purpose of using ORDERED_NODE_SNAPSHOT_TYPE.
Reporter | ||
Comment 1•17 years ago
|
||
Assignee | ||
Updated•17 years ago
|
Flags: blocking1.9?
Assignee | ||
Comment 2•17 years ago
|
||
Yeah, this is looking bad. We should simply keep an nsCOMArray<> of all the nodes in the snapshot.
Assignee | ||
Updated•17 years ago
|
Assignee: nobody → jonas
Flags: blocking1.9? → blocking1.9+
Assignee | ||
Comment 3•17 years ago
|
||
This should be fixed by the patch in bug 402208
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•17 years ago
|
Flags: in-testsuite?
You need to log in
before you can comment on or make changes to this bug.
Description
•