Contact emailsmsten...@chromium.org ExplainerNone
Specificationhttps://drafts.csswg.org/cssom/#the-csspagerule-interface Summary Let CSSPageRule inherit from CSSGroupingRule instead of CSSRule. The spec [1] says that the CSSPageRule interface should inherit from CSSGroupingRule, but Blink inherits from CSSRule instead. In order to support @page margins (CSSMarginRule), CSSPageRule needs to support child rules. [1] https://drafts.csswg.org/cssom/#the-csspagerule-interface [2] https://drafts.csswg.org/css-page-3/#syntax-page-selector Blink componentBlink>CSS <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS> TAG reviewNone TAG review statusNot applicable Risks Interoperability and Compatibility Low risk. The one possible issue is if an author uses "instanceof CSSGroupingRule" or "instanceof CSSRule" with a page rule object and makes incorrect assumptions based on that. However, given that this is already shipping in Firefox (and also that in Firefox, even CSSStyleRule inherits from CSSGroupingRule, as the spec says - whereas Blink still doesn't), the risk should be very low. *Gecko*: Shipped/Shipping ( https://bugzilla.mozilla.org/show_bug.cgi?id=1868215) *WebKit*: No signal *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? None Debuggability None 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 Flag name on chrome://flagsNone Finch feature nameNone Non-finch justification There's no way to make such a change behind a runtime feature flag, so this will just have to ship when the code change lands. In the worst case, it will have to be reverted. Requires code in //chrome?False Tracking bughttps://issues.chromium.org/issues/324827379 Estimated milestones Shipping on desktop 126 Shipping on Android 126 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). None Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5218866421825536?gate=6703446991568896 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 blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKWZFm6A_ym0LTCu88g0-3Z3VgCR61aR9%3Do1qe6sNYpGGOckdg%40mail.gmail.com.