Intent to Ship: The revert-rule Keyword
Anders Hartvoll Ruud
Contact emails
Explainer
https://github.com/w3c/csswg-drafts/blob/main/css-cascade-5/revert-rule-explainer.md
Specification
https://drafts.csswg.org/css-cascade-5/#revert-rule-keyword
Summary
The revert-rule keyword rolls back the cascade to the previous rule, similar to how revert-layer rolls back the cascade to the previous layer. For example:
div { color: green; }
div { color: revert-rule; /* Effectively green */ }
This is especially useful in combination with conditionals, as it allows eliminating the current rule if some condition is not met:
div {
display: if(style(--layout: fancy): grid; else: revert-rule);
}
Blink component
Web Feature ID
No information provided
Motivation
No information provided
Initial public proposal
https://github.com/w3c/csswg-drafts/issues/10443
TAG review
https://github.com/w3ctag/design-reviews/issues/1193 (Recently filed)
TAG review status
Pending
Risks
Interoperability and Compatibility
No information provided
Gecko: No signal (https://github.com/mozilla/standards-positions/issues/1358) (Recently filed)
WebKit: No signal (https://github.com/WebKit/standards-positions/issues/617) (Recently filed)
Web developers: No signals
Other signals:
WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
No information provided
Debuggability
The new keyword is clickable, leading to the reverted-to declaration.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
Yes
Is this feature fully tested by web-platform-tests?
Yes
https://wpt.fyi/results/css?label=master&label=experimental&aligned&q=revert-rule
Flag name on about://flags
No information provided
Finch feature name
CSSRevertRule
Rollout plan
Will ship enabled for all users
Requires code in //chrome?
False
Tracking bug
https://issues.chromium.org/issues/393582263
Estimated milestones
Note: This I2S is targeting 148 (next milestone + 1) to give other vendors and TAG a reasonable time window to raise any concerns.
Anticipated spec changes
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
No information provided
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5146458504429568?gate=5104230520193024
Links to previous Intent discussions
Intent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKFBnUrPRGxEbO1Uz3NnLJongnyknP%2BQ3zTRdpP%3DeFEJiza-Zg%40mail.gmail.com
This intent message was generated by Chrome Platform Status.