I'm sorry, it's too late. Currently, the HTML spec 
<https://html.spec.whatwg.org/multipage/canvas.html#dom-context-2d-letterspacing>
 
says
   
   1. 
   
   Let parsed be the result of parsing 
   <https://drafts.csswg.org/css-syntax/#parse-grammar> the given value as 
   a CSS <length> <https://drafts.csswg.org/css-values/#lengths>.
   
So, I intent to implement the percentage unit support for 
context-2d-letterspacing separately at a later time.

Thank you.
2025년 12월 8일 월요일 PM 7시 21분 41초 UTC+9에 一丝님이 작성:

> I'm wondering if `CanvasRenderingContext2D.letterSpacing` and 
> `CanvasRenderingContext2D.wordSpacing` should also support percentage 
> values? 
>
> Currently, it seems this isn't implemented.
>
> 在2025年11月12日星期三 UTC+8 23:15:38<Daniel Bratell> 写道:
>
>> I am sorry for the missing mail.
>>
>> LGTM1 from me so now you have the three necessary LGTMs. I hope the delay 
>> hasn't caused too many problems.
>>
>> /Daniel
>> On 2025-11-07 18:59, Mike Taylor wrote:
>>
>> Sure, let's do this in reverse order: LGTM2
>>
>> (both Daniel and I have already approved on chromestatus)
>> On 11/7/25 4:54 a.m., Philip Jägenstedt wrote:
>>
>> LGTM3 as you already have two LGTMs on the original thread. 
>>
>> @Mike Taylor @Daniel Bratell would you mind repeating your LGTMs here 
>> and on the chromestatus entry?
>>
>> On Thu, Nov 6, 2025 at 9:04 PM Minseong Kim <[email protected]> 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>
>>>
>>> *Motivation*
>>> The 'letter-spacing' and 'word-spacing' properties currently only accept 
>>> fixed length values (e.g. px, em), which are inflexible in responsive 
>>> designs. When font sizes or container dimensions change, this fixed spacing 
>>> can become disproportionate, forcing developers to write complex media 
>>> queries or use JavaScript to maintain readable text. Introducing percentage 
>>> values allows spacing to be defined relative to font-intrinsic metrics. 
>>> This enables both letter and word spacing to scale proportionally with the 
>>> font, simplifying the creation of robust and visually consistent typography 
>>> across all devices without extra code.
>>>
>>> *Initial public proposal*
>>> *No information provided*
>>>
>>> *Search tags*
>>> letter-spacing <https://chromestatus.com/features#tags:letter-spacing>, 
>>> word-spacing <https://chromestatus.com/features#tags:word-spacing>
>>>
>>> *TAG review*
>>> *No information provided*
>>>
>>> *TAG review status*
>>> Not applicable
>>>
>>> *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
>>>
>>>
>>> *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
>>> - "letter-spacing-*.html" files in 
>>> https://wpt.fyi/results/css/css-text/parsing
>>> - "word-spacing-*.html" files in 
>>> https://wpt.fyi/results/css/css-text/parsing
>>>
>>> *Flag name on about://flags*
>>> enable-experimental-web-platform-features
>>>
>>> *Finch feature name*
>>> CSSLetterAndWordSpacingPercentage
>>>
>>> *Rollout plan*
>>> Will ship enabled for all users
>>>
>>> *Requires code in //chrome?*
>>> False
>>>
>>> *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/5106867491700736?gate=6484265969778688
>>>
>>> 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-R6VKL-Muuq-FDTD9KL0prpPyRny00TCCmYmue6L17Hdyg%40mail.gmail.com
>>>  
>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BLL-R6VKL-Muuq-FDTD9KL0prpPyRny00TCCmYmue6L17Hdyg%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/CAARdPYebYDApQqccJ_9kxjD4hNz3PRTAL%2BPSUzyn_A6fKNe2qw%40mail.gmail.com
>>  
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYebYDApQqccJ_9kxjD4hNz3PRTAL%2BPSUzyn_A6fKNe2qw%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/34b3a017-6a38-498b-b247-fce353fb8cf8n%40chromium.org.

Reply via email to