Re: [csswg-drafts] [css-text] Consider different keyword for `line-break: break-all`?

The CSS Working Group just discussed `line-break: break-all`, and agreed to the following resolutions:

* `RESOLVED: Rename line-break:break-all to line-break:anywhere.`
* `RESOLVED: After edits from this meeting, publish new WD of Text 3.`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> Topic: line-break: break-all<br>
&lt;Rossen> github topic: https://github.com/w3c/csswg-drafts/issues/1561<br>
&lt;TabAtkins> Florian: line-break:break-all isn't a great name. Should we find a better name?<br>
&lt;TabAtkins> Florian: I think all names are bad, but I can't come up with a good one.<br>
&lt;TabAtkins> Florian: This value allows line-breaks everywhere.<br>
&lt;TabAtkins> Florian: word-break:break-all allows for breaks between letters, but not between punctuations, spaces, etc.<br>
&lt;TabAtkins> line-break is terminal wrapping, word-break is just hyphens-wherver-you-want<br>
&lt;TabAtkins> Florian: Trying to do better ignoring web constraints is hard, trying to do better *with* web compat is near impossible.<br>
&lt;TabAtkins> Florian: line-break:break-all is the newest one, with best chance of renaming.<br>
&lt;TabAtkins> Florian: Unforutnately it's got the best name, I think.<br>
&lt;TabAtkins> koji: I don't mean it's badly named, just that same keyword on similar property doing differently is confusing.<br>
&lt;TabAtkins> koji: Particularly if we have a shorthand for both hof these.<br>
&lt;TabAtkins> fantasai: shorthands can do custom syntax; we'll definitely redesign the whole thing if we do a shorthand<br>
&lt;TabAtkins> fantasai: Shorthand would be *great*, we can make it all make sense<br>
&lt;TabAtkins> zakim, shut up and go awya<br>
&lt;Zakim> I don't understand 'shut up and go awya', TabAtkins<br>
&lt;TabAtkins> koji: I understand it's possible, but if we're naming now, why choose "break-all"?<br>
&lt;TabAtkins> fantasai: We didn't have a better one.<br>
&lt;TabAtkins> koji: Line-break:terminal?<br>
&lt;fantasai> Rossen: anywhere?<br>
&lt;fantasai> Rossen: any?<br>
&lt;fantasai> Rossen: all?<br>
&lt;fantasai> TabAtkins: That would force a break between every character<br>
&lt;TabAtkins> [a few people like anywhere]<br>
&lt;fantasai> Rossen: anyone care?<br>
&lt;fantasai> TabAtkins: I think re-using the keyword is bad<br>
&lt;fantasai> [several other ppl care]<br>
&lt;TabAtkins> Rossen: So from the people paying attention, any objections to renaming break-all to anywhere?<br>
&lt;TabAtkins> dbaron: How widely implemented?<br>
&lt;TabAtkins> fantasai: Nowhere, it's new, we added it this year.<br>
&lt;TabAtkins> RESOLVED: Rename line-break:break-all to line-break:anywhere.<br>
&lt;TabAtkins> Florian: I have a PR for this change; other than me changing this keyword, can the editors approve it or tell me what's wrong?<br>
&lt;TabAtkins> fantasai: Yeah, at lunchb.<br>
&lt;TabAtkins> RESOLVED: After edits from this meeting, publish new WD of Text 3.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1561#issuecomment-320210579 using your GitHub account

Received on Friday, 4 August 2017 10:14:35 UTC