- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Apr 2018 01:39:08 +0000
- To: public-css-archive@w3.org
No, by "required" I mean "to avoid overflow". E.g., consider this code (using Latin text because I'm not familiar enough with the CJK case): ```html <div style="max-width: 10ch">super-cali-fragil-istic-expe-ale-docious</div> <div style="max-width: 10ch">supercalifragilisticexpealedocious</div> ``` Unless automatic hyphenation is turned on, the second one overflows. But the first one wraps at the hyphens, because hyphens are normally considered break opportunities in English text. So the question is, is it enough to say that the user agent MAY break text at the hyphen, or is it better to say that they SHOULD consider the hyphen a break opportunity when fitting text to layout constraints? Or another example, what about the "/" character? ```html <div style="max-width: 10ch">super/cali/fragil/istic/expe/ale/docious</div> ``` I personally think that text layout SHOULD support breaks after a slash (especially for URLs and path strings, but also for "and/or" type grammatical use), but most browsers don't implement it that way. (Firefox does! So much nicer!) The other browsers are "allowed" to break after the slash, but they never do, even if the result is overflowing text. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2450#issuecomment-378795778 using your GitHub account
Received on Thursday, 5 April 2018 01:39:17 UTC