- From: r12a via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Apr 2018 11:50:07 +0000
- To: public-css-archive@w3.org
> So to check that a browser allows a break where it is supposed to, you need to craft a situation where not only the line could be wrapped there to avoid overflow, but also where this is the only place where you can possibly wrap. Which is exactly what my tests at https://w3c.github.io/i18n-tests/results/line-breaking etc do. But I'm trying to decide whether or not to send them to WPT repo, because if we do we are saying that we _expect_ such a behaviour. What such tests also do is point up that situations where a browser doesn't break under such conditions there seems to be a pretty clear indication of a problem. It can render the text unreadable. (In particular, the tests seem to reveal that Firefox uses adhoc information about linebreaking behaviour, and is missing information for certain characters, rather than using the Unicode data.) **Perhaps the spec should say, explicitly, that browsers SHOULD break a line at the nearest allowed break point before the line end (as defined by the rules given for loose, normal, and strict) unless it uses additional rules that would override that behaviour.** -- GitHub Notification of comment by r12a Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2450#issuecomment-380777999 using your GitHub account
Received on Thursday, 12 April 2018 11:50:17 UTC