- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Jun 2017 16:23:48 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `word-break: break-all doesn't break before sentence-ending punctuation if UAX #14 is used`, and agreed to the following resolutions: * `RESOLVED: line-break: break-all on its own has the effect of allowing breaks everywhere` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: word-break: break-all doesn't break before sentence-ending punctuation if UAX #14 is used<br> <Florian> Github: https://github.com/w3c/csswg-drafts/issues/1171<br> <dael> Florian: Title is a bit old. Now, at the last F2F we agreed to add a break-all value to line-break that might, in isolation allow breaks anywhere and everywhere. We did not decide if this should work on its own or if putting it on line-break should only effect punctuation<br> <dael> Florian: We said impl would prefer it work on its own and it appeared unlikely there were use cases to have breaks around punctuation but not inside words, but we weren't sure.<br> <dael> Florian: I tried to ping i18n but there has been no answer<br> <dael> fantasai: I asked on the telecons, they said they had not heard of a use case<br> <dael> Florian: So we should have line-break: break-all have effects on its own.<br> <dael> fantasai: I agree<br> <dael> Rossen_: In the absense of other recommendations from i18n or any other proposals, do we resolve?<br> <dael> fantasai: I think we can.<br> <dael> Rossen_: Any other opinions or options before we resolve?<br> <dael> Florian: Proposal: Line-break: break-all on its own has the effect of allowing breaks everywhere<br> <dael> Rossen_: Objections?<br> <dael> RESOLVED: line-break: break-all on its own has the effect of allowing breaks everywhere<br> <dael> Rossen_: Is this a change to the current spec?<br> <dael> Florian: Yes, we're adding this new value.<br> <dael> Rossen_: And this is L3 or 4 of text?<br> <dael> Florian: I've made a pull for L3 but I'm not sure we resolved either way<br> <dael> Rossen_: fantasai, preference?<br> <dael> fantasai: I don't. I think the feature is so simple it could be in 3.<br> <dael> fantasai: We can mark at-risk<br> <dael> Rossen_: Okay.<br> <dael> Rossen_: We'll add it to L3<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1171#issuecomment-310132214 using your GitHub account
Received on Wednesday, 21 June 2017 16:23:54 UTC