Closed
Bug 1980210
Opened 4 months ago
Closed 3 months ago
Chrome-Only `CSSStyleRule#querySelectorAll` doesn't support `@scope`
Categories
(DevTools :: Inspector: Rules, defect, P3)
DevTools
Inspector: Rules
Tracking
(firefox144 fixed)
RESOLVED
FIXED
144 Branch
| Tracking | Status | |
|---|---|---|
| firefox144 | --- | fixed |
People
(Reporter: dshin, Assigned: dshin)
References
Details
(Whiteboard: [at-scope-m2])
Attachments
(2 files)
Used here. Uses element.querySelectorAll() behind the scenes.
Similar to CSSScopeRule#selectorMatchesElement, tracked in bug 1934914.
Use of querySelectorAll doesn't make sense if there's a scope rule along the parent chain (querySelectorAll dodges this issue because the selectors are supplied as string, which cannot be encased in a scope rule).
| Assignee | ||
Comment 1•4 months ago
|
||
This affects the little square button inside inspector's "This Element" panel where it highlights all matching elements.
STR:
- Load attached testcase
- Inspect the green box
- Note that it is green because it matches the scope rule, whereas the red one doesn't.
- Click on the square beside the scoped rule ("Highlight all elements matching this selector")
Expected: Only the green box is highlighted
Actual: Both green and red boxes are highlighted
Updated•3 months ago
|
Severity: -- → S3
Priority: -- → P3
| Assignee | ||
Updated•3 months ago
|
Whiteboard: [at-scope-triage]
| Assignee | ||
Updated•3 months ago
|
Assignee: nobody → dshin
Status: NEW → ASSIGNED
| Assignee | ||
Comment 2•3 months ago
|
||
Pushed by dshin@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/ddb7b52487f1
https://hg.mozilla.org/integration/autoland/rev/099f2e619500
Support @scope in ChromeOnly CSSStyleRule.querySelectorAll. r=firefox-style-system-reviewers,devtools-reviewers,layout-reviewers,emilio,nchevobbe
Status: ASSIGNED → RESOLVED
Closed: 3 months ago
status-firefox144:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 144 Branch
Updated•2 months ago
|
QA Whiteboard: [qa-triage-done-c145/b144]
You need to log in
before you can comment on or make changes to this bug.
Description
•