As a data point, I see that the flag in STP is called "CSS text-spacing property", which suggests all 3 properties behind a single flag. It might not ship together, but it's a good guess.
On Thu, Feb 1, 2024 at 12:02 PM Philip Jägenstedt <foo...@chromium.org> wrote: > Hi Koji, > > Thanks for linking the tests, judging just by the test names it looks like > many combinations of languages and fonts are tested. Some of the tests are > failing though, is that expected? > > Also, I see that some of the tests don't actually use text-spacing-trim, > are those just testing default behaviors or what's the reason? > > The design doc says "This version implements a subset of the values > defined in the spec", is that still accurate, or is there support for all > of space-all | normal | trim-auto | trim-start | space-first | trim-all? > > Finally, since text-spacing-trim and text-autospace are longhands > for text-spacing, what is the plan for text-spacing? Will we introduce the > shorthand later together with text-autospace? That should mean that > something like `text-spacing: trim-all` won't work initially, even though > it doesn't involve text-autospace. But on the other hand shipping the > shorthand without text-autospace would break `text-spacing: punctuation` > and similar. I don't have a suggestion here, but can you clarify what the > overall plan is? > > Best regards, > Philip > > On Wed, Jan 31, 2024 at 6:38 AM Koji Ishii <ko...@chromium.org> wrote: > >> Contact emailsko...@chromium.org, lin...@chromium.org >> >> ExplainerNone >> >> Specification >> https://drafts.csswg.org/css-text-4/#text-spacing-trim-property >> >> Design docs >> >> https://docs.google.com/document/d/146Bupkg3nrNALL3bm8UElRd0vsLVH5807xubsnrthDw/edit?usp=sharing >> >> Summary >> >> Applies the kerning to CJK punctuation characters to produce the visually >> pleasing typography as defined by JLREQ (Requirements for Japanese Text >> Layout) and CLREQ (Requirements for Chinese Text Layout). Many CJK >> punctuation characters include glyph-internal spacing. For example, the CJK >> full stop and the CJK close parenthesis usually have glyph-internal >> spacings on the right half of their glyph spaces, to give them a constant >> advance as other ideographic characters. But when they appear in a row, the >> glyph-internal spacings become excessive. This feature adjusts such >> excessive spacing. This feature adjusts the glyph-internal spacing for 1) >> adjacent characters (pair kerning), 2) at the line start, and 3) at the >> line end, by using the font data. >> >> >> Blink componentBlink>Layout>Inline >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ELayout%3EInline> >> >> TAG reviewhttps://github.com/w3ctag/design-reviews/issues/907 >> >> TAG review statusNot applicable >> >> Risks >> >> >> Interoperability and Compatibility >> >> None >> >> >> *Gecko*: Positive ( >> https://github.com/mozilla/standards-positions/issues/903) >> >> *WebKit*: Positive (https://github.com/w3c/csswg-drafts/issues/4246) A >> flag is available in Safari Technology Preview. >> >> *Web developers*: Positive ( >> https://twitter.com/fontplus/status/1405020633600233479) This tweet >> about a web font provider in Japan providing this feature in fonts got 485 >> likes as of Aug 2023. >> >> *Other signals*: Parts of the feature is shipping in Android 13, >> ChromeOS 90, iOS 17, MS Word 6.0, and LibreOffice. >> >> 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? >> >> None >> >> >> Debuggability >> >> None >> >> >> Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, ChromeOS, 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 >> >> >> https://wpt.fyi/results/css/css-text?label=experimental&label=master&aligned&q=text-spacing-trim >> >> >> Flag name on chrome://flagsNone >> >> Finch feature nameNone >> >> Non-finch justificationNone >> >> Requires code in //chrome?False >> >> Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1463891 >> >> Sample links >> https://output.jsbin.com/figixaq >> >> Estimated milestones >> Shipping on desktop 123 >> Shipping on Android 123 >> Shipping on WebView 123 >> >> 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). >> None >> >> Link to entry on the Chrome Platform Status >> https://chromestatus.com/feature/5170044014690304 >> >> Links to previous Intent discussionsIntent to prototype: >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHe_1dKP6u%2BXJ5Vi9aH_AVHJiFPoUM7BhSTYX-oRTPxz87c5XQ%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. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHe_1dLUB%3D%3Dt8Qp102HDPUQiuM1qAG_da3bb44mG22FAVP%3Dk6A%40mail.gmail.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHe_1dLUB%3D%3Dt8Qp102HDPUQiuM1qAG_da3bb44mG22FAVP%3Dk6A%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/CAARdPYdLh0unRu4VdcH-ckx7Z-M5Bs0bdQ58aU9dWnycLoWnwQ%40mail.gmail.com.
