W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2011

[whatwg] Interaction of <wbr> and CSS white-space

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Mon, 16 May 2011 21:07:27 -0400
Message-ID: <4DD1CA4F.3030309@mit.edu>
On 5/16/11 8:34 PM, Aryeh Gregor wrote:
> On Mon, May 16, 2011 at 7:27 PM, Boris Zbarsky<bzbarsky at mit.edu>  wrote:
>> Whether to prioritize is a CSS issue.  Whether there's a breakpoint at all
>> after the 'f' in the string "y = f(1)" is a quality of implementation issue,
>> imo.
>
> Slightly tangential, but I once saw a page that displayed fine in
> Gecko but broke horribly in WebKit because of the difference in
> line-breaking algorithms.  There was a really long string in a user
> comment which Gecko broke over multiple lines but WebKit treated as
> unbreakable, with the result that WebKit stretched the page so it was
> unreadable.  I think it would be pretty nice if we were to spec
> line-breaking behavior -- UAX#14 specifies an algorithm that, as far
> as I can tell, is reasonably simple and much better than any browser
> now has.  (Although I can't say whether it would be acceptable for
> performance or other considerations.)

I'm not a line-breaking expert.  I'm pretty sure that the people who 
wrote the Gecko line-breaking code are very familiar with UAX#14, 
though, based on their code comments and bug comments.  I'd suggest 
asking for their input on why Gecko does something different from UAX#14 
if we're considering specifying it.

-Boris
Received on Monday, 16 May 2011 18:07:27 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:33 UTC