I am very supportive of this feature being worked on, but I am very puzzled by Google's intent to ship something that is different from the spec. It doesn't seem that you have expressed any disagreement with what the spec says, or asked for it to be changed. If you think the spec's design is wrong somehow, the CSS-WG needs to be made aware of that, so that we can look into your feedback and address it accordingly. If you think the spec's design is right, then why take the risk to ship something subtly incompatible with it, which could cause a compat problem that will eventually prevent you (and everyone else) from shipping the thing we (apparently) agree is right?
—Florian co-editor of the css-text spec > On 1Mar 2023, at 1:00, Koji Ishii <ko...@chromium.org> wrote: > > Contact emails > ko...@chromium.org <mailto:ko...@chromium.org> > > Explainer > None > > Specification > https://w3c.github.io/csswg-drafts/css-text-4/#valdef-text-wrap-balance > <https://w3c.github.io/csswg-drafts/css-text-4/#valdef-text-wrap-balance> > > Design docs > > https://docs.google.com/document/d/16-T9gqCagJxcST6hcnneSb7qGunxXa37_UHYqMqhPL0/edit?usp=sharing > > <https://docs.google.com/document/d/16-T9gqCagJxcST6hcnneSb7qGunxXa37_UHYqMqhPL0/edit?usp=sharing> > > Summary > Adjusts the lengths of lines in a paragraph balanced, for better readability > and to prevent typographic widows. This feature is often used in headlines. > > > Blink component > Blink>Layout>Inline > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ELayout%3EInline> > > TAG review > https://github.com/w3ctag/design-reviews/issues/822 > <https://github.com/w3ctag/design-reviews/issues/822> > > TAG review status > Issues open > > Risks > > > Interoperability and Compatibility > > > Gecko: No signal (https://github.com/mozilla/standards-positions/issues/755 > <https://github.com/mozilla/standards-positions/issues/755>) > > WebKit: No signal (https://github.com/WebKit/standards-positions/issues/143 > <https://github.com/WebKit/standards-positions/issues/143>) > > Web developers: Positive > (https://twitter.com/jensimmons/status/1542264788029423616 > <https://twitter.com/jensimmons/status/1542264788029423616>) > > Other signals: > > WebView application risks > Does this intent deprecate or change behavior of existing APIs, such that it > has potentially high risk for Android WebView-based applications? > No. > > > Debuggability > > > Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, Android, and Android WebView)? > Yes > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>? > Yes > > Flag name > > > Requires code in //chrome? > False > > Tracking bug > https://bugs.chromium.org/p/chromium/issues/detail?id=1251079 > <https://bugs.chromium.org/p/chromium/issues/detail?id=1251079> > > Estimated milestones > 113 > > > Anticipated spec changes > Open questions about a feature may be a source of future web compat or > interop issues. Please list open issues (e.g. links to known github issues in > the project for the feature specification) whose resolution may introduce web > compat/interop risk (e.g., changing to naming or structure of the API in a > non-backward-compatible way). > he CSS spec is still in early stage, it may be renamed, or the value may be > moved to other properties, in that case, we may want to keep the current > syntax for a while. > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5196960707903488 > <https://chromestatus.com/feature/5196960707903488> > > Links to previous Intent discussions > Intent to prototype: > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHe_1dLq4OOXCNoYEWOnmb%3D6oxbSw1urndHj%3Dmb8JtowhRyBvQ%40mail.gmail.com > > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHe_1dLq4OOXCNoYEWOnmb%3D6oxbSw1urndHj%3Dmb8JtowhRyBvQ%40mail.gmail.com> > > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org > <mailto:blink-dev+unsubscr...@chromium.org>. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHe_1d%2B-YUM4_3ceOMkajB6BNK3WtkYhv3b3wOxQHrciTtWbqg%40mail.gmail.com > > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHe_1d%2B-YUM4_3ceOMkajB6BNK3WtkYhv3b3wOxQHrciTtWbqg%40mail.gmail.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5A9EBAFF-0951-4D89-944B-71E0199D1257%40rivoal.net.
