Closed Bug 1557100 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 17188 - Implement forced-color-adjust CSS property

Categories

(Core :: CSS Parsing and Computation, defect, P4)

defect

Tracking

()

RESOLVED FIXED
mozilla69
Tracking Status
firefox69 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync upstream])

Sync web-platform-tests PR 17188 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/17188
Details from upstream follow.

Alison Maher <almaher@microsoft.com> wrote:

Implement forced-color-adjust CSS property

This change adds support for the forced-color-adjust CSS property and
adds a forced colors priority type. The forced colors priority type was
added because forced-color-adjust can affect high and low priority CSS
property types. Adding a new priority type allows forced-color-adjust
to be evaluated at a higher priority.

This change also updates the update_use_counter_css.py script to update
enums.xml based on
UseCounterHelper::MapCSSPropertyIdToCSSSampleIdForHistogram rather
than the old location in UseCounter.

Spec:
https://www.w3.org/TR/css-color-adjust-1/#forced-color-adjust-prop

Bug: 970285
Change-Id: I74759517a4d8be092b3b75301baca8a707c22ce7
Reviewed-on: https://chromium-review.googlesource.com/1644498
WPT-Export-Revision: ba4936805308d53dbd05e9c533cc52c59969bdd9

Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Failed to get results from try push
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/41978d40e433 [wpt PR 17188] - Implement forced-color-adjust CSS property, a=testonly
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
Whiteboard: [wptsync downstream] → [wptsync upstream]
You need to log in before you can comment on or make changes to this bug.