Intent to Ship: Unprefix CSS 'line-break' property

[Koji Ishii]

Contact emails ko...@chromium.org,qyearsley@chromium.org Spec https://drafts.csswg.org/css-text-3/#line-break-property Summary The CSS 'line-break' property specifies the strictness of line-breaking rules. The exact definition of the strictness depends on languages. Our implementation relies on ICU (see doc link) which supports East Asian writing systems and Finnish. Motivation

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. Interoperability risk

None. Firefox: Public support Edge: Shipped Safari: Shipped Web developers: Strongly positive (crbug.com/240344, Japanese stackoverflow)

Compatibility risk

None. Ongoing technical constraints

None. Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? Yes or no.

Yes.

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.

OWP launch tracking bug https://crbug.com/735539 Link to entry on the Chrome Platform Status https://www.chromestatus.com/features/5137645088800768 Requesting approval to ship?

Yes.

Apologies in advance, but we have shipped the unprefixed version unintentionally in M58, and that this is a post facto intent due to our errors. More details in style-dev@ discussion.

The UMA counts 0.5% (or 0.4% for -webkit- prefix.)

[TAMURA, Kent]

LGTM1.

It's unfortunate that it was accidentally shipped.  However, it's worth to ship, and it seems some CLs to prevent us from such accidental ship are on-going.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACQRE%2BTW6CSiQson09VCoeT-YuJNFzhd-5ffQaKChrhD7hG1gQ%40mail.gmail.com.

--

TAMURA Kent
Software Engineer, Google

[Mike West]

Whoops!

LGTM2. It looks like https://chromium-review.googlesource.com/c/551877/ and https://chromium-review.googlesource.com/c/551400 will prevent us from repeating this mistake in the future, and I agree with tkent@ that it's worth shipping.

Given that Edge and Safari have already shipped this unprefixed, is there a bug against Firefox that y'all could ping to update them on Blink's support as well?

-mike

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqFYDBSqq5Nj0%3D-WdbvYvgZc0G4uHkuB0RFgW3txy%3DQ_Ug%40mail.gmail.com.

[Koji Ishii]

On Wed, Jun 28, 2017 at 6:45 PM, Mike West <mk...@chromium.org> wrote:

Given that Edge and Safari have already shipped this unprefixed, is there a bug against Firefox that y'all could ping to update them on Blink's support as well?

3 years old bug here.​ I'll leave comments on our status, thank you for checking.

[Rick Byers]

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?

Regardless, LGTM3

--

You received this message because you are subscribed to the Google Groups "blink-dev" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACQRE%2BQ7%2BmLPH1z-ZktCTSpcZntzumr5vVmNT%2ByYmOzfWbHu-w%40mail.gmail.com.

[Koji Ishii]

On Wed, Jun 28, 2017 at 10:35 PM, Rick Byers <rby...@chromium.org> wrote:

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.

 

Regardless, LGTM3

​Thank you as always.​

[Rick Byers]

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).