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

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

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

fantasai
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

Reply | Threaded
Open this post in threaded view
|

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

Mike Taylor
On 8/16/16 3: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?

In this past this prop/val combo was known to break Google Play[1] and
Wired.com[2] (but those have since been updated/re-designed). That said,
it's all over the web and it wouldn't surprise me if more sites
depending on it. Curious if the Edge folks have more data.

(I wrote about this a few years back at [3] and dholbert corrected me at
[4]).

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=968994
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=959735
[3] https://miketaylr.com/posts/2014/01/word-break-break-word.html
[4] https://bugzilla.mozilla.org/show_bug.cgi?id=959735#c22

--
Mike Taylor
Web Compat, Mozilla

Reply | Threaded
Open this post in threaded view
|

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

Daniel Holbert-3
In reply to this post by fantasai
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
with).

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.

~Daniel



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
>

Reply | Threaded
Open this post in threaded view
|

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

Koji Ishii
Blink tried to remove, but failed as some sites relied on its minor different behavior.

See http://crbug.com/492202 for more details. There Bogdan said he agreed to add, so we resolved it as WontFix.

/koji

2016-08-17 6:11 GMT+09:00 Daniel Holbert <[hidden email]>:
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
with).

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.

~Daniel



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
>