Intent to Ship: CSS ruby-align property

317 views
Skip to first unread message

TAMURA, Kent

unread,
Jun 5, 2024, 6:14:33 PMJun 5
to blink-dev

Contact emails

tk...@chromium.org

Explainer

None

Specification

https://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 component

Blink>Layout>Ruby

Search tags

cssruby

TAG review

None; Firefox already shipped this.

TAG review status

Not 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?

Yes

"ruby-align*" files in https://wpt.fyi/results/css/css-ruby and https://wpt.fyi/results/css/css-rubyparsing



Flag name on chrome://flags

enable-experimental-web-platform-features

Finch feature name

CssRubyAlign

Requires code in //chrome?

False

Tracking bug

https://issues.chromium.org/issues/40249572

Estimated milestones

Shipping on desktop128
DevTrial on desktop127
Shipping on Android128
DevTrial on Android127
Shipping on WebView128


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 discussions

Intent 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.

--
TAMURA Kent
Software Engineer, Google


chrishtr via Chromestatus

unread,
Jun 6, 2024, 12:39:27 PMJun 6
to blin...@chromium.org
LGTM

Chris Harrelson

unread,
Jun 6, 2024, 12:40:04 PMJun 6
to chrishtr via Chromestatus, blin...@chromium.org
Sorry, make that "LGTM1"

On Thu, Jun 6, 2024 at 9:39 AM chrishtr via Chromestatus <admin+c...@cr-status.appspotmail.com> wrote:
LGTM

--
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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/000000000000eba2d9061a3b5258%40google.com.

Mike Taylor

unread,
Jun 6, 2024, 9:28:38 PMJun 6
to Chris Harrelson, chrishtr via Chromestatus, blin...@chromium.org

Vladimir Levin

unread,
Jun 7, 2024, 12:55:29 PMJun 7
to Mike Taylor, Chris Harrelson, chrishtr via Chromestatus, blin...@chromium.org
Reply all
Reply to author
Forward
0 new messages