Contact emails
jja0...@gmail.com
Specification
https://drafts.csswg.org/css-ruby/#ruby-overhang
Summary
Support of new CSS property `ruby-overhang` is added.
The property accepts one of `auto` and `none` keywords, and controls overhang of ruby annotation text.
Blink component
Blink>Layout>Ruby
Web Feature ID
ruby-overhang
Motivation
A ruby annotation can sometimes obscure adjacent content when it overhangs. The ruby-overhang property gives authors a way to disable this behavior and prevent unwanted overlap.
Initial public proposal
No information provided
Search tags
css,
ruby
TAG review
No information provided
TAG review status
Not applicable
Goals for experimentation
None
Risks
Interoperability and Compatibility
Risks are low. This is a support for new value of CSS properties. So sites not using properties won't be affected. Safari has supported this feature for years.
Gecko: No signal
WebKit: Shipped/Shipping (
https://bugs.webkit.org/show_bug.cgi?id=114678)
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
Debuggability
No information provided
Will this feature be supported on all six Blink platforms
(Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
Yes
Yes
"ruby-overhang*" files in
https://wpt.fyi/results/css/css-ruby
Flag name on about://flags
enable-experimental-web-platform-features
Finch feature name
CSSRubyOverhang
Rollout plan
Will ship enabled for all users
Requires code in //chrome?
False
Tracking bug
https://issues.chromium.org/issues/366873207
Estimated milestones
| Shipping on desktop | 148 |
| Shipping on Android | 148 |
| Shipping on WebView | 148 |
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/6560118298771456?gate=6494196590575616
Links to previous Intent discussions
Intent to Prototype:
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ffa95dff-f582-41cb-b0a5-d80159656284n%40chromium.org