Closed Bug 3333 Opened 26 years ago Closed 26 years ago

[RDF/DOM] Node parenting gets messed up when you add nodes to the RDF DOM

Categories

(Core Graveyard :: RDF, defect, P2)

Product:
Core Graveyard
Component:
RDF
Platform:
All
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: waterson, Assigned: waterson)

Details

This is the "node recycling" problem that I've talked about, where calls to "move" nodes in the DOM actually end up creating new DOM nodes, and the old references in JS variables become invalid. I'll get a test case put up soon; just wanted to log this as a bug so I'd remember not to forget it.
Component: Aurora/RDF BE → RDF
Product: MozillaClassic → Browser
Version: 1998-03-31 → other
Status: NEW → ASSIGNED
Target Milestone: M4
Set target milestone to M4.
Set target milestone to M5.
Target Milestone: M5 → M6
Moving to M6. Hyatt and I have a _lot_ of work to do on the XUL content model and this'll probably just get picked up there.
Target Milestone: M6 → M7
Blocks: 7403
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
This should have been fixed last week.
No longer blocks: 7403
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.