- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Dec 2016 04:25:19 +0000
- To: public-css-archive@w3.org
> From a user feedback and for consistency with other 3 browsers, I'm changing Blink to prioritize hyphens over break-word. Sounds good to me. Also, the spec already requires it: > break-word > An otherwise unbreakable sequence of characters may be broken at an arbitrary point **if there are no otherwise-acceptable break points in the line**. We could change it, but I don't think we should. ---- > This leaves a question whether hyphens should win over break-all, or opposite. Based on the spec, break-all should win: > break-all > [...] Hyphenation is not applied. That said, as we've been discussing in #785, there is a use case for hyphenation to apply as well in some cases. One way to do that is to introduce a new value like `break-all-hyphenate`, another would be to look at the `hyphens` property to decide if a hyphen should be inserted or not at the wrapping point. Not entirely sure we should support this, but if we do, I think the first alternative is better. So we could change the spec, but I don't think we should, and webkit should get fixed. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/791#issuecomment-265352400 using your GitHub account
Received on Wednesday, 7 December 2016 04:25:25 UTC