W3C home > Mailing lists > Public > public-css-archive@w3.org > December 2016

Re: [csswg-drafts] [css-text-3] Priority between break-all/break-word/hyphens

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Thu, 15 Dec 2016 09:33:50 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-267281432-1481794429-sysbot+gh@w3.org>
>>    Based on the spec, break-all should win:
>> >       break-all
>>>        [...] Hyphenation is not applied.
> IIRC this sentence doesn't intend that; its intention is "can break 
at non-hyphenation points, and does not insert hyphenation character,"
 because we thought otherwise it may be misunderstood for Latin 
speakers.

Sure, but if you do "break at non-hyphenation points, and does not 
insert hyphenation character", then how/when can you still hyphenate?

Let's assume that you have have `hyphens:auto` and `line-break: 
break-all`, that the line contains the word "today" which has a 
hyphenation opportunity between o and d. If the line has room for 3 
characters, we break (without hyphen) after d, since 
`line-break:break-all` creates a soft wrap opportunity between every 
letter. If the line has room for 2 characters, we should break after 
the o, but we cannot insert the hyphen, since that "to-" would be 3 
characters, which doesn't it. So we break after the o without a hyphen
 because `line-break:break-all` creates a soft wrap opportunity 
between every letter and because it tells us that hyphenation does not
 apply.

I don't quite see what else could happen without inventing rules that 
are not in the spec.


-- 
GitHub Notification of comment by frivoal
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/791#issuecomment-267281432 
using your GitHub account
Received on Thursday, 15 December 2016 09:33:56 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:30:27 UTC