Oh, I've created a new chromestatus entry and sent an Intent to Ship mail.
He doesn't need to convert this on the backend. Thanks for your help!
https://chromestatus.com/feature/5106867491700736

2025년 11월 5일 (수) 오후 10:51, Mike Taylor <[email protected]>님이 작성:

> I wonder if Jason Robbins (cc'd) could convert this on the backend, so
> Minseong doesn't have to request new reviews, etc.
> On 11/4/25 7:29 p.m., TAMURA, Kent wrote:
>
> It seems the chromestatus entry has an incorrect feature type, and API
> owners can't approve it.
> Minseong, would you re-create an entry with "Chromium catches up" feature
> type please?
>
>
> On Wed, Nov 5, 2025 at 12:48 AM Mike Taylor <[email protected]>
> wrote:
>
>> LGTM1
>> On 10/28/25 10:05 a.m., Minseong Kim wrote:
>>
>> *Contact emails*
>> [email protected]
>>
>> *Specification*
>> https://www.w3.org/TR/css-text-4/#propdef-letter-spacing
>> https://www.w3.org/TR/css-text-4/#propdef-word-spacing
>>
>> *Summary*
>> Enables percentage values for the letter-spacing and word-spacing CSS
>> property, as defined in the CSS Text Module Level 4 spec. Percentage values
>> are calculated relative to the advance measure of the space character
>> (U+0020). This gives developers more robust and flexible control over
>> typography, particularly in responsive designs where text spacing needs to
>> adapt to different viewports and font sizes.
>>
>> *Blink component*
>> Blink>Layout>Inline
>> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ELayout%3EInline%22>
>>
>> *Web Feature ID*
>> letter-spacing <https://webstatus.dev/features/letter-spacing>
>>
>> *Search tags*
>> letter-spacing <https://chromestatus.com/features#tags:letter-spacing>,
>> word-spacing <https://chromestatus.com/features#tags:word-spacing>
>>
>> *Risks*
>>
>>
>> *Interoperability and Compatibility*
>> Risks are low. This is a support for new value of CSS properties. So
>> sites not using properties won't be affected. Firefox and Safari has
>> supported this feature for years.
>>
>> *Gecko*: Shipped/Shipping Firefox is failing so many letter-spacing
>> tests:
>> https://wpt.fyi/results/css/css-text/letter-spacing?label=experimental&label=master&aligned.
>> But those are related the line ending or boundary handling of
>> letter-spacing, not the percentage values. Related discussion:
>> https://github.com/w3c/csswg-drafts/issues/1518
>>
>> *WebKit*: Shipped/Shipping (https://github.com/WebKit/WebKit/pull/18771)
>>
>> *Web developers*: No signals (
>> https://issues.chromium.org/issues/327740939) The issue has 3 votes.
>>
>> *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 information provided*
>>
>>
>> *Debuggability*
>> *No information provided*
>>
>> *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
>> - "letter-spacing-percentage-001.html" file in
>> https://wpt.fyi/results/css/css-text/letter-spacing -
>> "word-spacing-percentage-001.html" file in
>> https://wpt.fyi/results/css/css-text/word-spacing
>>
>> (aside, I see there are a few more relevant tests at
>> https://github.com/web-platform-tests/wpt/commit/ffae172a1c2e44bddf71ca9430bc2aa519fbff6e)
>>
>>
>>
>>
>> *Tracking bug*
>> https://issues.chromium.org/issues/327740939
>>
>> *Estimated milestones*
>> Shipping on desktop 145
>> Shipping on Android 145
>> Shipping on WebView 145
>> Shipping on iOS 145
>>
>> *Link to entry on the Chrome Platform Status*
>> https://chromestatus.com/feature/5074916059381760
>>
>> 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 [email protected].
>> To view this discussion visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BLL-R5oXaEwW3KnnPK0rzdYqXSmxM18X_0b6KZUZ-XCejkmoQ%40mail.gmail.com
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BLL-R5oXaEwW3KnnPK0rzdYqXSmxM18X_0b6KZUZ-XCejkmoQ%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 [email protected].
>> To view this discussion visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/384b8855-9a42-4504-8c61-221cccc49d9f%40chromium.org
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/384b8855-9a42-4504-8c61-221cccc49d9f%40chromium.org?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> --
> TAMURA Kent
> Software Engineer, Google
>
>
>

-- 
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 [email protected].
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BLL-R6p5RgQebye-zdmNOAXhj3BKUfk3kWOozPiwy64foEi%2BQ%40mail.gmail.com.

Reply via email to