Closed
Bug 1440713
Opened 7 years ago
Closed 2 years ago
[wpt-sync] Sync PR 8150 - Fix #8122: Upstream Mozilla counter-style tests
Categories
(Core :: CSS Parsing and Computation, enhancement, P3)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
113 Branch
Tracking | Status | |
---|---|---|
firefox113 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
References
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 8150 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/w3c/web-platform-tests/pull/8150
Details from upstream follow.
Geoffrey Sneddon wrote:
> Fix #8122: Upstream Mozilla counter-style tests
>
> These don't cover all of the counter styles, but they give us automated tests for most of them.
>
> They are all originally authored by @dbaron and @upsuper.
>
> Fixes #8122.
>
>
>
Reporter | ||
Updated•7 years ago
|
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Reporter | ||
Comment 1•6 years ago
|
||
Updated•2 years ago
|
Severity: normal → S3
Reporter | ||
Updated•2 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Reporter | ||
Updated•2 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Reporter | ||
Comment 2•2 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=19c152556e4f7b809292c85eee8862a32ec66076
Reporter | ||
Comment 3•2 years ago
|
||
CI Results
Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 14 tests
Status Summary
Firefox
PASS
: 14
Chrome
PASS
: 8
FAIL
: 6
Safari
PASS
: 9
FAIL
: 5
Links
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/85e2b9f9787e
[wpt PR 8150] - Fix #8122: Upstream Mozilla counter-style tests, a=testonly
Comment 5•2 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox113:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 113 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•