Closed
Bug 83839
Opened 24 years ago
Closed 24 years ago
make first-node/last-node rules in quirks.css non-universal
Categories
(Core :: CSS Parsing and Computation, defect, P2)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
mozilla0.9.2
People
(Reporter: dbaron, Assigned: dbaron)
References
Details
(Keywords: perf, Whiteboard: [whitebox])
The first-node and last-node rules in quirks.css don't need to be universal --
we can split them so they have tag selectors for each tag on which we specify a
margin in html.css or quirks.css. This will considerably cut the time we spend
in SelectorMatches in page loading.
(The first-node / last-node check could be pulled out into the
SelectorMatchesData construction, but I think we only do 3 checks total per
content node right now, so that wouldn't help much. However, the above patch
would still help considerably when combined with lazy computation of said values
in the SelectorMatchesData as proposed in bug 83834.
Assignee | ||
Updated•24 years ago
|
Assignee | ||
Comment 2•24 years ago
|
||
I checked in this fix on 2001-06-08.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Updated•22 years ago
|
Whiteboard: [whitebox]
You need to log in
before you can comment on or make changes to this bug.
Description
•