Re: [csswg-drafts] [css-text-3] Implement or unship word-break:break-word (#2390)

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

* `RESOLVED: add word-break:break-word to text level 3, with a note`

<details><summary>The full IRC log of that discussion</summary>
&lt;fremy> Topic: word-break: break-word<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/2390<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/2390<br>
&lt;fremy> emilio: Blink cannot seem to be able to unship<br>
&lt;dbaron> https://bugzilla.mozilla.org/show_bug.cgi?id=1296042<br>
&lt;fremy> emilio: We considered the alternatives<br>
&lt;fremy> emilio: but the usage in Blink is very high so even if they also implemented the alternatives<br>
&lt;fremy> emilio: they would not unship<br>
&lt;fremy> emilio: I'm tired of getting new compat issues about this<br>
&lt;fremy> emilio: so, can we maybe as a group add this to a spec?<br>
&lt;fremy> emilio: maybe even mark it as deprecated<br>
&lt;fremy> emilio: it's sad but realistic<br>
&lt;fremy> florian: I am annoyed that this means we will have to care about this forever<br>
&lt;fremy> florian: but I guess if this is required, I guess we will have to live with it<br>
&lt;fremy> florian: because both the name is bad, but also it's not on the right property<br>
&lt;fremy> florian: but well...<br>
&lt;fremy> florian: ...<br>
&lt;fremy> florian: is anybody sad enough that they are willing to object?<br>
&lt;fremy> (so far no noise is heard)<br>
&lt;fremy> emilio: we could put it in a webcompat spec?<br>
&lt;fremy> florian: no, if we do it, let's do it properly<br>
&lt;fremy> florian: as in, the text spec<br>
&lt;fremy> astearns: so, all seem resigned to accept this at this point, is that right?<br>
&lt;fantasai> s/(so far no noise is heard)/&lt;giggles>/<br>
&lt;fremy> astearns: proposed resolution is thus to add it (back) to the spec<br>
&lt;fremy> fantasai: we have to decide if we put it in the same table as the other values<br>
&lt;fremy> fantasai: or in a prose section further down below<br>
&lt;fremy> astearns: I like the latter<br>
&lt;fremy> astearns: level 3 or level 4?<br>
&lt;fremy> fantasai: level 3 because it is not CR yet<br>
&lt;fremy> dholbert: are we confident we can get this specced properly soon though?<br>
&lt;fremy> fantasai: yes, we already have this exact behavior, just on another property<br>
&lt;fremy> AmeliaBR: so we will have two values doing the same thing?<br>
&lt;fremy> fantasai: yes<br>
&lt;fremy> AmeliaBR: how will they interact<br>
&lt;fremy> emilio: either or both would trigger this behavior<br>
&lt;fremy> AmeliaBR: ok, seems reasonable<br>
&lt;fremy> emilio: either must work on their own for compat<br>
&lt;fremy> astearns: so, any object to add this to text level 3? with the explanation that people should use the other property?<br>
&lt;fremy> RESOLVED: add word-break:break-word to text level 3, with a note<br>
</details>


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

Received on Wednesday, 27 February 2019 01:24:40 UTC