Remove color-gamut's status override
#3711
Open
+12
−11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
feature definition
captainbrosset
approved these changes
Jan 29, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This removes the editorial override for the
color-gamutCSS media query. The underlying data is correct: this media query is supported. Though Firefox doesn't have support for displays with a wider gamut than sRGB, it correctly reports this fact through the media query. To help developers understand this distinction, I've opened mdn/browser-compat-data#28892 on BCD to add notes and close a related upstream issue.This retroactively sets the Baseline high date to 2025-08-14. I think this is the right call since there was no actual issue that should have held the status to a later date (it was only our indecision that made it so).
We discussed this on the WebDX call today, where no objections were voiced to removing this override.
Fixes #3227