Contact emailstk...@chromium.org ExplainerNone
Specificationhttps://drafts.csswg.org/css-ruby/#ruby-align-property Summary Support of a new CSS property `ruby-align` is added. The property accepts one of `space-around` `space-between` `start` and `center` keywords, and controls alignment of ruby base text and ruby annotation text. Blink componentBlink>Layout>Ruby <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ELayout%3ERuby> Search tagscss <https://chromestatus.com/features#tags:css>, ruby <https://chromestatus.com/features#tags:ruby> TAG reviewNone; Firefox already shipped this. TAG review statusNot applicable Risks Interoperability and Compatibility Risks are low. This is an addition of new CSS property. So sites not using this property won't be affected. Firefox has supported this feature for years. *Gecko*: Shipped/Shipping *WebKit*: Support (https://github.com/WebKit/standards-positions/issues/232) WebKit is positive about the whole specification, but the position for this specific property is unknown. *Web developers*: Strongly positive ( https://issues.chromium.org/issues/40249572) The issue has 23 votes. *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 "ruby-align*" files in https://wpt.fyi/results/css/css-ruby and https://wpt.fyi/results/css/css-rubyparsing Flag name on chrome://flagsenable-experimental-web-platform-features Finch feature nameCssRubyAlign Requires code in //chrome?False Tracking bughttps://issues.chromium.org/issues/40249572 Estimated milestones Shipping on desktop 128 DevTrial on desktop 127 Shipping on Android 128 DevTrial on Android 127 Shipping on WebView 128 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/5152412192210944 Links to previous Intent discussionsIntent to prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqEWiJevj%2B2-%2BvR%2B6FOC61YOAaozVd%3DM%3DoY3AzN%3DiOp4%2Bg%40mail.gmail.com This intent message was generated by Chrome Platform Status <https://chromestatus.com/>. -- TAMURA Kent Software Engineer, Google -- 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/CAGH7WqGpVTwpGrX4-bcKdzJAT9LfEzgoKC2O4yNWRF_-YDr5Dg%40mail.gmail.com.