Intent to Ship: Update the syntax of `text-wrap` to match the new spec
Koji Ishii
Contact emails
ko...@chromium.orgExplainer
NoneSpecification
https://drafts.csswg.org/css-text-4/#text-wrap-shorthandDesign docs
https://docs.google.com/document/d/1Xl3J1WCg--fUm1-FX5gHbJIIC0szNwulQV7nW4n6_aY/edit?usp=sharing
Summary
Updates the CSS syntax for the CSS white-space and text-wrap properties to match the spec and other browsers. Blink changed the CSS white-space property in crbug.com/40257360, shipped in M114. The CSS white-space and text-wrap properties have changed since then, and other browsers are shipping the new behavior. This feature makes Blink match the new spec and other browsers.
Blink component
Blink>Layout>InlineTAG review
NoneTAG review status
Not applicableRisks
Interoperability and Compatibility
None
Gecko: Shipped/Shipping
WebKit: Shipped/Shipping (https://bugs.webkit.org/show_bug.cgi?id=249840)
Web developers: Positive
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)?
YesIs this feature fully tested by web-platform-tests?
YesFlag name on chrome://flags
NoneFinch feature name
NoneNon-finch justification
NoneRequires code in //chrome?
FalseEstimated milestones
| Shipping on desktop | 130 |
| Shipping on Android | 130 |
| Shipping on WebView | 130 |
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).
NoneLink to entry on the Chrome Platform Status
https://chromestatus.com/feature/5793719555719168?gate=4921803110350848Links to previous Intent discussions
Intent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHe_1dL3Mj5%2Bkq0T25Kd49RkU1zQMqNe1X1%3DvbxbemJ_SAhaow%40mail.gmail.com
Domenic Denicola
Contact emails
ko...@chromium.orgExplainer
NoneSpecification
https://drafts.csswg.org/css-text-4/#text-wrap-shorthandDesign docs
https://docs.google.com/document/d/1Xl3J1WCg--fUm1-FX5gHbJIIC0szNwulQV7nW4n6_aY/edit?usp=sharingSummary
Updates the CSS syntax for the CSS white-space and text-wrap properties to match the spec and other browsers. Blink changed the CSS white-space property in crbug.com/40257360, shipped in M114. The CSS white-space and text-wrap properties have changed since then, and other browsers are shipping the new behavior. This feature makes Blink match the new spec and other browsers.
Blink component
Blink>Layout>InlineTAG review
NoneTAG review status
Not applicableRisks
Interoperability and Compatibility
None
Gecko: Shipped/Shipping
WebKit: Shipped/Shipping (https://bugs.webkit.org/show_bug.cgi?id=249840)
Web developers: Positive
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)?
YesIs this feature fully tested by web-platform-tests?
YesFlag name on chrome://flags
NoneFinch feature name
NoneNon-finch justification
None
Requires code in //chrome?
FalseEstimated milestones
Shipping on desktop 130 Shipping on Android 130 Shipping on WebView 130 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).
NoneLink to entry on the Chrome Platform Status
https://chromestatus.com/feature/5793719555719168?gate=4921803110350848Links to previous Intent discussions
Intent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHe_1dL3Mj5%2Bkq0T25Kd49RkU1zQMqNe1X1%3DvbxbemJ_SAhaow%40mail.gmail.comThis intent message was generated by Chrome Platform Status.
--
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/CAHe_1dLqVwf839yLgTK6UEeiP4409KhuWohH0idJXOOxZDu7dg%40mail.gmail.com.
Koji Ishii
Will there be any compatibility issues, i.e. code that means something different before and after the change?
The risk is considered low for the reasons below:
- It's more common to use the `text-wrap` property for these values than to use the `white-space` property, as articles such as https://developer.chrome.com/docs/css-ui/css-text-wrap-balance suggest using the `text-wrap` property.
- Gecko and WebKit didn't ship the old spec behavior, and thus they never supported these values for the `white-space` property.
- When there were breaks, at worst, balancing or the Knuth-Plass algorithm don't apply, but the text is still readable in reasonably good layout.
Alex Russell
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
Mike Taylor
LGTM2
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/f90074a8-71e0-4f8f-af5c-8178d41144a1n%40chromium.org.
Daniel Bratell
LGTM3
/Daniel
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/8bf5c706-66b9-4ea0-bddb-9ef02059f106%40chromium.org.