Re: [csswg-drafts] [css-text] Prevent line breaking after explicit hyphens (#3434)

Chiming in with a testcase documenting state in 2025 how `word-break: keep-all;` relates to **`width: min-content`** with hyphenated words in Latin script in different browsers.

Test: http://myfonj.github.io/tst/width-min-content-word-break-keep-all.html 

Results: 

| WebKit (Playwright) | Firefox | Chrome |
| -- | -- | -- |
| ![AppleWebKit/605.1.15 `keep-all` makes hyphenated words unbroken](https://github.com/user-attachments/assets/552c8807-9eb4-455d-9b46-5b57fde7e650) | ![Firefox/140 `keep-all` makes hyphenated words unbroken](https://github.com/user-attachments/assets/1618492e-3f7b-477c-b4be-5ee535c8742e) | ![Chrome/135 `keep-all` lets hyphenated words break the same way `normal` does](https://github.com/user-attachments/assets/c3126098-6773-4353-90f0-535370eb4a26) |

This is basically [what Šime demonstrated](#issuecomment-1751613149) already.

It shows that some browsers interpret `word-break: keep-all;` as a signal to skip break opportunities on hyphens when looking for the minimum intrinsic size of the content width, while other does not. (Got here from [issue report](https://issues.chromium.org/issues/415076052) indicating the outlier is not incorrect after all.)

I see that officially the `keep-all` is not intended for Latin script whatsoever (?), so technically the different outcome for `normal` and `keep-all` of the testcase in the first two instances is really a spec violation at this point (?).

Will this remain this way?

If so, issues for the *other* browsers should be filled ASAP (I guess) since it seems like an interop issue already.

-- 
GitHub Notification of comment by myfonj
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3434#issuecomment-2930534577 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 2 June 2025 12:47:54 UTC