Re: [csswg-drafts] [css-text-3] word-wrap/overflow-wrap: break-word should affect min-content

The CSS Working Group just discussed `word-wrap/overflow-wrap: break-word should affect min-content`, and agreed to the following:

* `RESOLVED: Add an anywhere keyword to overflow-wrap`

<details><summary>The full IRC log of that discussion</summary>
&lt;heycam> Topic: word-wrap/overflow-wrap: break-word should affect min-content<br>
&lt;heycam> github: https://github.com/w3c/csswg-drafts/issues/2682<br>
&lt;astearns> (summary: https://github.com/w3c/csswg-drafts/issues/2682#issuecomment-431503466 )<br>
&lt;heycam> florian: we have 2 things. we have overflow-wrap:break-word<br>
&lt;heycam> ... which says that if the line is too long, apply line breaking, if it still doesn't fit, break anywhere<br>
&lt;heycam> ... it doesn't affect intrinsic size<br>
&lt;heycam> ... if you have text in a table cell that says if i'm too long wrap anywhere, because teh table cell is sized to the intrinsic size<br>
&lt;heycam> ... same thing in flex boxes and some other situations<br>
&lt;heycam> ... we should have had overflow-wrap:break-word affect intrinsic size<br>
&lt;heycam> ... Mozilla found it's not web compatible to do that<br>
&lt;heycam> ... WebKit an Chrome have that switch, which doesn't the same thing as overflow-wrap:break-word plus intrinsic sizing, but it's on the wrong property<br>
&lt;heycam> ... the word-wrap property<br>
&lt;heycam> ... so there is some web compat pressure, but not an overwhelming amount, since even tho we've been talking about this for a while, both Edge and Firefox have resisted implementing it<br>
&lt;heycam> ... given that overflow-wrap:break-word should have done the right thing, we should add a new value that does so<br>
&lt;heycam> ... overflow-wrap:anywhere<br>
&lt;heycam> ... we already have an anywhere value in another overflow property<br>
&lt;heycam> ... line-break:anywhere allows it all the time, overflow-wrap:anywhere is only if you need to break<br>
&lt;heycam> ... maybe that will be enough and the web will slowly learn to use that rather than the WebKit thing<br>
&lt;heycam> ... if it turns out not to be the case, we should have both, rather than just breaks the property that otherwise makes sense<br>
&lt;heycam> eae: I agree with that<br>
&lt;fantasai> s/that/that, it makes sense to spec the right behavior and we would support that/<br>
&lt;heycam> florian: I propose we resolve on adding overflow-wrap:anywhere, we don't resolve on word-break:break-word, but only come back to that if web compat forces us to<br>
&lt;heycam> RESOLVED: Add an anywhere keyword to overflow-wrap<br>
&lt;heycam> myles: are overflow-wrap / word-wrap no longer going to be synonyms?<br>
&lt;heycam> Rossen: no they are<br>
</details>


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

Received on Monday, 22 October 2018 10:36:12 UTC