Closed
Bug 1809659
Opened 2 years ago
Closed 2 years ago
[wpt-sync] Sync PR 37877 - [css-selectors-4] Add a test for invalidation of ancestors within :nth-child().
Categories
(Core :: CSS Parsing and Computation, task, P4)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
111 Branch
Tracking | Status | |
---|---|---|
firefox111 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 37877 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/37877
Details from upstream follow.
Steinar H. Gunderson <sesse@chromium.org> wrote:
[css-selectors-4] Add a test for invalidation of ancestors within :nth-child().
Change-Id: Ie332cb862f0a497a35486444a8a763b082b22a60
Reviewed-on: https://chromium-review.googlesource.com/4154957
WPT-Export-Revision: 500dc3c2bf812874bdf2f07f84555cee89a448bc
Assignee | ||
Updated•2 years ago
|
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Assignee | ||
Comment 1•2 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=5da192c69c99543f70cd1e25f68da591d966705e
Updated•2 years ago
|
Blocks: nth-child-of
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/48df53e6d1f9
[wpt PR 37877] - [css-selectors-4] Add a test for invalidation of ancestors within :nth-child()., a=testonly
https://hg.mozilla.org/integration/autoland/rev/59f4b4f1f694
[wpt PR 37877] - Update wpt metadata, a=testonly
Assignee | ||
Comment 3•2 years ago
|
||
Test result changes from PR not available.
Comment 4•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/48df53e6d1f9
https://hg.mozilla.org/mozilla-central/rev/59f4b4f1f694
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox111:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
Updated•2 years ago
|
No longer blocks: nth-child-of
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•