W3C home > Mailing lists > Public > www-style@w3.org > August 2016

Re: [css-text] word-break: break-word

From: Daniel Holbert <dholbert@mozilla.com>
Date: Tue, 16 Aug 2016 14:11:04 -0700
To: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <3ebf1ff4-4876-630a-5094-4bccaf15598e@mozilla.com>
I expect this is in response to issues like these:
  https://bugzilla.mozilla.org/show_bug.cgi?id=959735 (Wired)
  https://github.com/webcompat/web-bugs/issues/1671 (LinkedIn)
  https://bugzilla.mozilla.org/show_bug.cgi?id=1136818 (random site)
...which are all cases where a site accidentally depends on nonstandard
"word-break: break-word". (which WebKit & Blink support, but other
engines do not)  This ends up producing text that either overflows off
the screen, or wraps in arbitrary places in the middle of short words
for no good reason (depending on what other CSS this style is combined

In each of these cases, the page's CSS could (and was) fixed by using
"word-wrap" instead of "word-break".  But if WebKit/Blink intend to keep
shipping this non-standard value indefinitely, it will probably continue
to create webcompat issues (particularly on mobile sites, where authors
tend to only test WebKit/Blink).

So, I'd be in favor of adding it to the spec, if WebKit/Blink aren't
intending to drop support.


On 08/16/2016 01:28 PM, fantasai wrote:
> Going through css-text-3 issues with astearns today...
> At Sydney we resolved
>   https://lists.w3.org/Archives/Public/www-style/2016Mar/0352.html
>   RESOLVED: Add word-break: break-word to spec if Edge/Firefox
>             find it critical enough to Web compat to implement it.
> Anyone from Gecko or Edge teams have further information on this issue?
> Be careful: there are several very similar-sounding property-value
> combinations, we're specifically interested in this one. ;)
> ~fantasai
Received on Tuesday, 16 August 2016 21:11:38 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:15:00 UTC