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

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

From: Koji Ishii <kojiishi@gmail.com>
Date: Tue, 2 Feb 2016 13:36:30 +1100
Message-ID: <CAN9ydbV1YR5tRNZ_a8gObjaT7gMe+mf6iVsXYLdco-R3CE9+OA@mail.gmail.com>
To: Florian Rivoal <florian@rivoal.net>
Cc: Bogdan Brinza <bbrinza@microsoft.com>, W3C www-style mailing list <www-style@w3.org>
Bogdan and I talked about this today, and agreed it's best to discuss in
the WG. In short:

* There are some minor different behaviors from other values.
* Usage is high (0.3% in Bogdan's study,) some sites such as yelp.com
depends on the behavior.
* yelp.com tried to replace but did not succeed.

In short, this value measures like word-break: break-all, but breaks like
word-wrap: break-word.

For more context, please see https://crbug.com/492202.

/koji

On Sun, May 24, 2015 at 1:04 PM, Florian Rivoal <florian@rivoal.net> wrote:

>
> > On 23 May 2015, at 02:33, Bogdan Brinza <bbrinza@microsoft.com> wrote:
> >
> > Hi,
> >
> > We've recently got an interoperability bug report for Microsoft Edge
> that was rooted in "word-break: break-word". Chrome in this case breaks as
> if overflow-wrap/word-wrap is set to break-word and Edge/Firefox don't.
> (example [1])
> >
> > Looking at the latest draft [2] I see the expected values for word-break
> don't include break-word, which lives as a property under
> overflow-wrap/word-wrap.
> >
> > I didn't find any existing bugs in Blink/WebKit for this property and
> brief web search shows there might be some WebKit history [3].
> >
> > Looking at the usage data word-break: break-word is used on 3000 sites
> from the set of 1 000 000 unique sites. Brief analysis suggests this might
> be mostly coming from couple JS libraries - but it doesn't look like any of
> them depend on it.
> >
> > What would be the right approach to solving this interop problem? Given
> the data so far it would make sense to file bugs to consider removing this
> from WebKit / Blink, unless I'm missing something?
>
> I agree that dropping it from Webkit / Blink sounds like the best way
> forward, assuming they are willing. Maybe we should get the JS libraries
> you mentioned fixed first, to prevent this value spreading too much, and
> people accidentally depending on it.
>
>  - Florian
>
Received on Tuesday, 2 February 2016 02:37:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:52:36 UTC