investigate removal of mDocument pointer from nsGeneric[HTML]Element

RESOLVED FIXED in Future

Status

()

Core
DOM: Core & HTML
P3
normal
RESOLVED FIXED
19 years ago
4 years ago

People

(Reporter: Chris Waterson, Assigned: Chris Waterson)

Tracking

({dom1, perf})

Trunk
Future
x86
Windows NT
dom1, perf
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

19 years ago
Per scc's suggestion, investigate time/space trade-offs from removing the 
cached mDocument pointer from nsGeneric[HTML]Element and nsXULElement, and 
instead doing an O(log n) walk to the root of the element to determine the 
document.
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED
Keywords: perf
Target Milestone: M15
(Assignee)

Updated

18 years ago
Target Milestone: M15 → M16
Waterson, hold on with doing this for a while, I've got other ideas up my
sleave, more info in a while...
(Assignee)

Updated

18 years ago
Target Milestone: M16 → Future

Comment 2

18 years ago
Mass update of qa contact
QA Contact: gerardok → janc
Any news, jst?  (How much would this save us, anyway?  How many of these things
do we create/keep in memory?  Thousands?  Millions?)
Keywords: nsbeta1
Keywords: dom1
Component: DOM Level 1 → DOM HTML

Comment 4

18 years ago
QA contact Update
QA Contact: janc → desale

Comment 5

17 years ago
Updating QA contact to Shivakiran Tummala.
QA Contact: desale → stummala

Updated

17 years ago
Blocks: 104166
Fixed as part of a checkin for bug 27382. Filed bug 255077 on a similar change
for nsXULElement.
Status: ASSIGNED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED

Updated

10 years ago
Component: DOM: HTML → DOM: Core & HTML
QA Contact: stummala → general
You need to log in before you can comment on or make changes to this bug.