[wpt-sync] Sync PR 33740 - [@scope] Evaluate scoped rules in SelectorChecker
Categories
(Core :: CSS Parsing and Computation, task, P4)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox102 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 33740 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/33740
Details from upstream follow.
Anders Hartvoll Ruud <andruud@chromium.org> wrote:
[@scope] Evaluate scoped rules in SelectorChecker
This CL propagates the enclosing StyleScope (if any) to
SelectorChecker, such that we can perform an additional check
(CheckInStyleScope) to see if the subject element is in scope.Several different approaches were considered, but in order to remain
agile with regards to the different paths the css-cascade-6
specification might take from this point, I opted to handle it
entirely within SelectorChecker, even if other approaches may be
more efficient. It is more important that the prototype is able to
handle alternative entry points to the feature (if needed) than it
is to have the best possible performance right away.Many performance optimizations are planned as follow-ups, most
notably:
- Making use of the fast reject filter.
- Multiple StyleScopeFrames with longer lifetimes.
Note also that addressing the following is deferred to future CLs:
- ShadowDOM
- Invalidation
Bug: 1280240
Change-Id: I050e7d8249688ae6d6d67431dceca5eabfbcc7fcReviewed-on: https://chromium-review.googlesource.com/3582131
WPT-Export-Revision: a5f7030d1968499873417393bd90dfa9ba03fa88
| Assignee | ||
Updated•4 years ago
|
| Assignee | ||
Comment 1•4 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/e66b18d2287a
https://hg.mozilla.org/mozilla-central/rev/a7ca0dd20f33
Description
•