The overflow-inline and overflow-block CSS properties allow setting overflow in inline and block direction relative to the writing-mode. In a horizontal writing-mode overflow-inline maps to overflow-x, while in a vertical writing-mode it maps to overflow-y.
The relevant properties overflow-block and overflow-inline are part of Interop 2025. Firefox already ships and It's highly likely that Safari also will ship this year.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
Will be possible to inspect and change via devtools like any other property. In particular the existing overflow properties.
https://wpt.live/css/css-overflow/inheritance.html https://wpt.live/css/css-overflow/logical-overflow-001.html https://wpt.live/css/css-overflow/parsing/overflow-computed.html https://wpt.live/css/css-overflow/parsing/overflow-invalid.html https://wpt.live/css/css-overflow/parsing/overflow-valid.html
Shipping on desktop | 135 |
DevTrial on desktop | 77 |
Shipping on Android | 135 |
DevTrial on Android | 77 |
Shipping on WebView | 135 |
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).
NoneOn 2/7/25 8:19 AM, Rune Lillesveen wrote:
Contact emails
fut...@chromium.org
Explainer
None
Specification
https://drafts.csswg.org/css-overflow-3/#overflow-control
Summary
The overflow-inline and overflow-block CSS properties allow setting overflow in inline and block direction relative to the writing-mode. In a horizontal writing-mode overflow-inline maps to overflow-x, while in a vertical writing-mode it maps to overflow-y.
Blink component
Blink>CSS
TAG review
None
TAG review status
Not applicable
Risks
Interoperability and Compatibility
The relevant properties overflow-block and overflow-inline are part of Interop 2025. Firefox already ships and It's highly likely that Safari also will ship this year.
Gecko: Shipped/Shipping
WebKit: Positive Accepted as part of interop 2025
--
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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACuPfeQo7ShHhKwRy5huKJZ1zt1Zj8WJu6B%3DpPifbbrWUPzyGA%40mail.gmail.com.
On 2/7/25 8:19 AM, Rune Lillesveen wrote:
2 years ago Apple indicated that they would prefer official position requests for anything related to Interop (see https://groups.google.com/a/chromium.org/g/blink-dev/c/HxqAcgnTs8o/m/I_Fx6FoRBQAJ). Until they've told us otherwise, can we do the same here?
--
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.
LGTM2
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/7d01bd60-0a49-460e-9891-e17232f02ea2%40chromium.org.