Enable the forced-colors media query
Categories
(Core :: CSS Parsing and Computation, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox89 | --- | fixed |
People
(Reporter: zekemedley, Assigned: morgan)
References
(Blocks 2 open bugs)
Details
(Keywords: dev-doc-complete)
Attachments
(1 file, 1 obsolete file)
(deleted),
text/x-phabricator-request
|
Details |
While at the moment forced-colors
is a subset of prefers-contrast: forced
it is possible that it is here to stay. Edge currently implements it and Bug 1591204 tracks its implementation behind layout.css.forced-colors.enabled
. Once we've determined that the spec is sufficiently finalized we should turn that pref on by default.
Reporter | ||
Comment 1•4 years ago
|
||
Here is the spec issue to watch for this right now. Based on the discussion on there, I'd hazard to say that forced-colors
will likely stick around in a way that is backwards compatible with the current spec. If that's the case, we may as well pref it on sooner rather than later.
Assignee | ||
Comment 2•4 years ago
|
||
Updated•4 years ago
|
Assignee | ||
Comment 3•4 years ago
|
||
Updated•4 years ago
|
Comment 5•4 years ago
|
||
bugherder |
Comment 6•4 years ago
|
||
I couldn't see any relevant code in Bug 1591204 - is the value protected by RFP (privacy.resistFingerprinting) - i.e always return
none`?
Comment 7•4 years ago
|
||
This will only return true when using forced colors mode / high contrast, which is highly observable via other means and fundamentally incompatible with resistFingerprinting (because we use real system colors for everything in that mode, basically).
I'd be ok with auto-disabling forced colors if resistFingerprinting is true, but there's no point in adding code particularly to the media query code (and it'd be a bit weird as forced colors is exposed in the preferences via other prefs, like browser.display.document_color_use
).
Comment 8•3 years ago
|
||
This was previously documented, so I've updated BCD, and added a release note.
Description
•