Intent to Implement: line-break: anywhere

80 views
Skip to first unread message

Javier Fernandez

unread,
Mar 3, 2019, 7:20:28 PM3/3/19
to blin...@chromium.org
Contact emails

jfern...@igalia.com

Spec
CSS Text Module Level 3
https://drafts.csswg.org/css-text-3/#line-break-property

Summary
The 'line-break: anywhere' feature ads a soft wrap opportunity around every typographic character unit, including around any punctuation character or preserved spaces, or in the middle of words, disregarding any prohibition against line breaks, even those introduced by characters with the GL, WJ, or ZWJ character class (see [UAX14]) or mandated by the word-break property.

Motivation

Chrome's implementation of the 'word-break: break-all' feature tries to match Edge, and the current spec draft, so that it ignores code points like "." (FULL STOP), which is categorized as IS. In UAX 14. However, end users seems to prefer Firefox's and Safair's behavior, although is not completely spec complaint. So, the CSS WG resolved to introduce a new value of the line-break property to complement what 'break-word: break-all'  provides (matching Firefox and Safari but also users expectations); additionally, it allows breaking at any reserved white-space, so in a way emulates the behavior of terminal-like text editors

Interoperability and Compatibility Risk

Low compatibility risk.

  • Since 'line-break: anywhere' is new value it won’t break existing web.

Medium interoperability risk


WebKit: https://webkit.org/b/181169 - positive signals
Gecko: https://bugzil.la/1531715 - no public signals
Edge: No public signals
Ongoing technical constraints

The feature will be implemented behind an experimental runtime flag.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

Yes.

OWP launch tracking bug

https://crbug.com/720205


Link to entry on the feature dashboard

https://www.chromestatus.com/features/5668660729348096


Requesting approval to ship?

No.

Joe Medley

unread,
Mar 4, 2019, 5:01:26 PM3/4/19
to Javier Fernandez, blin...@chromium.org
Javier,

Can you give me a tracking bug for this. The link in the status entry for user-select:contain and the one in your intent doesn't work at all.

Joe
Joe Medley | Technical Writer, Chrome DevRel | jme...@google.com | 816-678-7195
If an API's not documented it doesn't exist.


--
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/72b123f8-8983-1924-00aa-54ec196ca8a8%40igalia.com.

Javier Fernandez

unread,
Mar 4, 2019, 6:38:23 PM3/4/19
to blin...@chromium.org
Sorry about the mistake in the tracking bug link; this is the correct one:

https://crbug.com/720205

Javier Fernandez

unread,
Mar 4, 2019, 6:44:05 PM3/4/19
to blin...@chromium.org
It seems the link to the chromestatus entry is also wrong, this is the correct one:

 https://www.chromestatus.com/feature/5668660729348096
Reply all
Reply to author
Forward
0 new messages