On Mon, May 16, 2011 at 5:34 PM, Aryeh Gregor <[email protected]> wrote: > On Mon, May 16, 2011 at 7:27 PM, Boris Zbarsky <[email protected]> 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 suspect you're thinking of the site I filed a bug against Webkit for: <https://bugs.webkit.org/show_bug.cgi?id=41103> ~TJ
