- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Sat, 19 May 2018 00:16:57 +0000
- To: public-css-archive@w3.org
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-text-3] word-wrap/overflow-wrap: break-word should affect min-content == See https://github.com/w3c/csswg-drafts/issues/2270#issuecomment-390053485 and https://github.com/w3c/csswg-drafts/issues/2390 //cc @Dan503 Right now word-wrap/overflow-wrap: break-word allows long words to wrap if they are too long to fit in the container, but in an auto-sized container, they will still force the container to grow. This is frustrating to authors. Issue 2390 is about adding a `break-word` value to `word-break` to address this feature (because WebKit/Blink happen to have implemented such a thing), but then we end up with two extremely similar-looking property-value pairs that do almost exactly the same thing except for this side-effect of how they influence the min-content size. The number of line-breaking controls in CSS is already crazy confusing; we really don't need to have the similarity between `word-wrap: break-word` and `word-break: break-word` compounding the situation. Also I suspect that making the already-existing `word-wrap: break-word` influence min-content sizes is a reasonable thing to do regardless: it can't do its job of allowing breaking if the container is forced to fit the thing that it's trying to break anyway. So the proposal is to make the existing `word-wrap/overflow-wrap` property affect intrinsic sizing and, hopefully, also close #2390 as no change. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2682 using your GitHub account
Received on Saturday, 19 May 2018 00:17:01 UTC