Moving content nodes between documents does not preserve uniquenes of content IDs

RESOLVED WORKSFORME

Status

()

Core
DOM: Core & HTML
RESOLVED WORKSFORME
16 years ago
6 years ago

People

(Reporter: Simon Fraser, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
If you write code that creates content nodes on document A:

docA->CreateElementNS(..., &newElement);

then appends them to document B:

nodeInDocB->AppendChild(newElement, ..);

then it's possible to get content node ID conflicts.

It would seem that copying or moving nodes between documents should ensure that
content IDs (gotten via GetContentID() remain unique for each document. If a
node is in 2 documents at the same time, then, I guess, it would have to have an
ID per document.
Content ID's are evil. If at all possible we should work on removing them in
stead of making them...

Updated

16 years ago
QA Contact: desale → stummala
Mass-reassigning bugs to dom_bugs@netscape.com
Assignee: jst → dom_bugs

Updated

10 years ago
Component: DOM: Core → DOM: Core & HTML
QA Contact: stummala → general
Looks like they were removed at some point.
Assignee: general → nobody
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.