Closed
Bug 143191
Opened 24 years ago
Closed 22 years ago
Investigate splitting up nsContentList into multiple classes
Categories
(Core :: DOM: Core & HTML, defect, P4)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
WONTFIX
Future
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
Details
(Keywords: helpwanted, memory-footprint, perf)
nsContentList currently uses _either_ mMatchAtom/mMatchNamespaceId _or_
mMatchFunc/mData; things like Match() branch on that difference, and different
constructors are used for the two types of content lists. This strongly
suggests that we should just have two separate classes, both of which should be
able to be smaller and faster as a result of having fewer members and having to
do fewer checks.
I'll investigate this sometime soonish, hopefully...
|
Assignee | |
Updated•24 years ago
|
|
|
Assignee | |
Updated•24 years ago
|
Priority: -- → P1
Target Milestone: --- → mozilla1.1beta
|
|
||
Updated•24 years ago
|
QA Contact: desale → stummala
|
|
Assignee | |
Updated•24 years ago
|
Target Milestone: mozilla1.1beta → mozilla1.2beta
|
|
Assignee | |
Updated•23 years ago
|
Target Milestone: mozilla1.2beta → mozilla1.3beta
|
|
Assignee | |
Updated•23 years ago
|
Target Milestone: mozilla1.3beta → Future
|
|
Assignee | |
Updated•23 years ago
|
Target Milestone: Future → mozilla1.5beta
|
|
Assignee | |
Comment 1•22 years ago
|
||
I've not thought of a decent way to do this yet. Futuring, and I doubt I will
ever get to this. It's not clear to me that the benefits of doing it, if any,
are worth it.
|
|
Assignee | |
Comment 2•22 years ago
|
||
Now that getElementsByAttribute() uses this class, comment 0 is no longer true.
There are no real benefits to splitting up at this point.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Component: DOM: Core → DOM: Core & HTML
QA Contact: stummala → general
You need to log in
before you can comment on or make changes to this bug.
Description
•