Closed Bug 433421 Opened 16 years ago Closed 14 years ago

Don't use nameless guard object

Categories

(Core :: DOM: Core & HTML, defect, P1)

defect

Tracking

()

RESOLVED FIXED

People

(Reporter: sicking, Assigned: sicking)

Details

I think the result of this is slower performance under some circumstances. Mostly when using .replaceChild which is pretty rare. Might have worse consequences than performance, but I'm less sure about that.

So I don't think this is a blocker, but I do think we should fix this if there is another RC.
This also affects document fragment (so innerHTML) performance, I would think.
innerHTML creates its own batch, so it's unaffected.
Thanks for filing this jonas - if it turns out to worse please re-nom.
Flags: wanted-next+
Flags: blocking1.9?
Flags: blocking1.9-
I think we should definitely take this on the branch...
Flags: wanted1.9.0.x?
Agreed
Flags: wanted1.9.0.x? → wanted1.9.0.x+
Priority: -- → P1
blocking2.0: --- → beta6+
Peter fixed this way back in bug 540848
Status: NEW → RESOLVED
blocking2.0: beta6+ → ---
Closed: 14 years ago
Resolution: --- → FIXED
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.