Closed
Bug 1867151
Opened 2 years ago
Closed 2 years ago
[wpt-sync] Sync PR 43399 - Allow non-percentages for hsl and hwb
Categories
(Core :: CSS Parsing and Computation, task, P4)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
122 Branch
| Tracking | Status | |
|---|---|---|
| firefox122 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 43399 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/43399
Details from upstream follow.
Aaron Krajeski <aaronhk@chromium.org> wrote:
Allow non-percentages for hsl and hwb
Bug: 1505787
Change-Id: Ie7fec239d0422da54a3d8ee0e46e64b1bee73fe2
Reviewed-on: https://chromium-review.googlesource.com/5067499
WPT-Export-Revision: 4681c12440f7d3e1d0288b2b6a3f02cf8c87eea2
| Assignee | ||
Updated•2 years ago
|
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
| Assignee | ||
Updated•2 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
| Assignee | ||
Updated•2 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
| Assignee | ||
Comment 1•2 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=4f7918d398a3a17b5fae139379ef204020f14ba6
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2b473eb31c3f
[wpt PR 43399] - Allow non-percentages for hsl and hwb, a=testonly
| Assignee | ||
Comment 3•2 years ago
|
||
Test result changes from PR not available.
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b2a173798a54
[wpt PR 43399] - Allow non-percentages for hsl and hwb, a=testonly
| Assignee | ||
Comment 5•2 years ago
|
||
Test result changes from PR not available.
Comment 6•2 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox122:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•