I see. Yes, very similar. So without revert-rule, it would basically be initial here as well (like with if)?
☆*PhistucK* On Wed, Feb 18, 2026 at 8:09 PM Anders Hartvoll Ruud <[email protected]> wrote: > On Wed, Feb 18, 2026 at 8:58 PM PhistucK <[email protected]> wrote: > >> The first example is a bit nonsensical... Is there a better example that >> does not involve if? >> > > This indeed needs to be combined with some kind of branching/conditional > to be useful. An example without if() would be (though ultimately similar): > > color: var(--maybe-invalid, revert-rule); > > >> On Tue, Feb 17, 2026 at 7:38 PM Vladimir Levin <[email protected]> >> wrote: >> >>> LGTM3 >>> >>> On Tue, Feb 17, 2026 at 2:27 PM Chris Harrelson <[email protected]> >>> wrote: >>> >>>> LGTM2 >>>> >>>> On Tue, Feb 17, 2026 at 11:24 AM Mike Taylor <[email protected]> >>>> wrote: >>>> >>>>> LGTM1 >>>>> On 2/16/26 12:40 p.m., Anders Hartvoll Ruud wrote: >>>>> >>>>> Contact emails >>>>> >>>>> [email protected] >>>>> >>>>> 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 >>>>> >>>>> Blink>CSS >>>>> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ECSS%22> >>>>> >>>>> 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 >>>>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >>>>> ? >>>>> >>>>> 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 >>>>> >>>>> Shipping on desktop >>>>> >>>>> 148 >>>>> >>>>> Shipping on Android >>>>> >>>>> 148 >>>>> >>>>> Shipping on WebView >>>>> >>>>> 148 >>>>> >>>>> 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 >>>>> <https://chromestatus.com/>. >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "blink-dev" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To view this discussion visit >>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKFBnUpcohOCEHaFeoDUh%2B49qF-UfRzHT-eQopUzBf8Myo%3Dfog%40mail.gmail.com >>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKFBnUpcohOCEHaFeoDUh%2B49qF-UfRzHT-eQopUzBf8Myo%3Dfog%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "blink-dev" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To view this discussion visit >>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/59b9ee51-8e43-4276-a832-e9194dfe335d%40chromium.org >>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/59b9ee51-8e43-4276-a832-e9194dfe335d%40chromium.org?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "blink-dev" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To view this discussion visit >>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9BxrG_cHFEzKkN%2BUUhqC18%3DvfXpGOLAdX7fe4J6-PsUQ%40mail.gmail.com >>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9BxrG_cHFEzKkN%2BUUhqC18%3DvfXpGOLAdX7fe4J6-PsUQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "blink-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion visit >>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADsXd2PoC5fELZPDo9Xf%2B347ic%2BB0_yyD8AUhOWEG4eHCBEuVQ%40mail.gmail.com >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADsXd2PoC5fELZPDo9Xf%2B347ic%2BB0_yyD8AUhOWEG4eHCBEuVQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABc02_J4pTv1aSrccCCcqt9OGzkg_prGThMCgyxe5s58K3%3D9GQ%40mail.gmail.com.
