New issue
Advanced search Search tips

Issue 638147 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 7
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Support strict child descendant invalidation sets

Reported by r...@opera.com, Aug 16 2016

Issue description

For :nth-selectors we use a descendant invalidation set which is scheduled for the parent of the mutated siblings. That means that if we have a selector ".x:nth-child(2n)", the invalidation set contains ".x". However, we know that these selectors only apply to direct children of the mutation parent. Currently, we will invalidate all ".x" descendants. This is not a big issue for class/id invalidations, but if the :nth-selector is not qualified, it means we'll have full subtree recalcs where recalc of just the direct children would be enough.

We could mark the invalidation set for :nth-selectors as applying to direct children only and have machinery in StyleInvalidator to cater for that.

 
Labels: Update-Quarterly
Labels: -Performance Performance-Loading
Project Member

Comment 3 by sheriffbot@chromium.org, Oct 19 2017

Labels: Hotlist-Recharge-BouncingOwner
Owner: ----
Status: Untriaged (was: Assigned)
The assigned owner "rune@opera.com" is not able to receive e-mails, please re-triage.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by nainar@chromium.org, Oct 19 2017

Labels: Hotlist-Reassign-In-Nov
Owner: nainar@chromium.org
Status: Assigned (was: Untriaged)
Labels: -Hotlist-Recharge-BouncingOwner -Hotlist-Reassign-In-Nov
Owner: futhark@chromium.org
Cc: futhark@chromium.org
Owner: ----
Status: Available (was: Assigned)
Labels: -Update-Quarterly
Project Member

Comment 8 by sheriffbot@chromium.org, Dec 6

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)
Probably a nice todo, but not a bug and probably won't be fixed any time soon.

Sign in to add a comment