Closed
Bug 449447
Opened 16 years ago
Closed 16 years ago
[FIX]Reuse the caching GetNthIndex for first/last/onlyChild selectors
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
Details
Attachments
(1 file)
6.58 KB,
patch
|
dbaron
:
review+
dbaron
:
superreview+
|
Details | Diff | Splinter Review |
See bug 128585 comment 13.
Attachment #332574 -
Flags: superreview?(dbaron)
Attachment #332574 -
Flags: review?(dbaron)
Comment on attachment 332574 [details] [diff] [review] Like so Is there a way we can make things assert if the content tree mutates during GetNthIndex? Maybe at least an NS_ASSERTION at the end that GetChildArray() still returns the same thing? (If there's some state we can push that would trigger such assertions elsewhere, even better.) Please add some :first-child, :last-child, and :only-child tests to test_selectors.html ? And maybe some for :first-node and :last-node too? (No need to do tons unless you want to, but we should have something.) r+sr=dbaron with that
Attachment #332574 -
Flags: superreview?(dbaron)
Attachment #332574 -
Flags: superreview+
Attachment #332574 -
Flags: review?(dbaron)
Attachment #332574 -
Flags: review+
Assignee | ||
Comment 2•16 years ago
|
||
> Is there a way we can make things assert if the content tree mutates > during GetNthIndex? I filed bug 451053 on this. Added some tests for this stuff. Pushed changeset a0a61f95d6aa.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•