Remove never-implemented CSS at-rule features#5122
Merged
chrisdavidmills merged 4 commits intomdn:mainfrom May 20, 2021
Merged
Conversation
This is sorta-kinda implemented in a way that's meaningless. It appears to have preserved as a convenience to spec authors: w3c/csswg-drafts#594 w3c/csswg-drafts#1778 w3c/csswg-drafts@2c28928
Contributor
chrisdavidmills
approved these changes
May 20, 2021
Contributor
chrisdavidmills
left a comment
There was a problem hiding this comment.
This all makes sense to me; thanks @ddbeck !
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In mdn/browser-compat-data#6944, we're dropping some features which are all-
false. In addition to being unsupported, these features don't show any sign of being implemented (i.e., a search of Firefox, Chrome, and WebKit bugs doesn't turn up any evidence of implementation—with one exception, below).https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-transparency
https://developer.mozilla.org/en-US/docs/Web/CSS/@media/scan
https://developer.mozilla.org/en-US/docs/Web/CSS/@page/bleed
https://developer.mozilla.org/en-US/docs/Web/CSS/@page/marks
mdn/browser-compat-data#6944
The
scanmedia query is exceptional: it may be partially implemented in Chrome, but it doesn't do anything (for obvious reasons, I couldn't confirm this via testing). It seems to have been retained as a convenience to specification authors. See d9c73be for details.