This is a long-demanded feature primarily from Japan, where words are not separated by spaces and different line-breaking rules are strongly desired depends on the types/styles of the documents. Web developers using such styles consider not using 'strict' rules is a bug in the product.
Originally shipped in IE5.5 in July 2000, defined in CSS Text Level 3 and EPUB 3, and recently Safari unprefixed.
The actual supported writing systems and levels of the strictness depend on the ICU data. Android, or some distributions, may chose to reduce the size of ICU data. See crbug.com/306730#c17 for more details.
Thanks for catching this and doing the post-hoc intent. Also thanks to Darren and Alan for quickly adding protection against this class of mistake.
What's the status of web-platform-tests for this feature?
Thank you for asking this, I missed to check that.
wpt has 556 tests created by Richard Ishida@W3C i18n WG. TestExpectations has 46 failures among them. Last I checked, some of them were caused by 1px rendering differences, while some needed more investigations, but I didn't record exact numbers.
The I18N WG site has results for each browsers, but Chrome result is before this property is supported. I'll work with Richard to update the results on his site with this property shipping.
Thank you as always.
Jun 28, 2017, 12:02:45 PM6/28/17
Reply to author
Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Report message as abuse
Sign in to report message as abuse
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Koji Ishii, Mike West, TAMURA, Kent, blink-dev, Quinten Yearsley, Alan Cutter, sh...@chromium.org
Sounds good, thanks~ In particular the top priority is probably ensuring that Chrome passes the tests which Edge and Safari are passing (we definitely don't want to be the ones holding back interop). Hopefully we'll have a dashboard soon that helps us easily find these cases :-) (w3.org is 503ing for me at the moment).