spec has been cleard, landing flag-flip now! :)  thank you!

[email protected] schrieb am Montag, 14. September 2026 um 23:11:00 
UTC+2:

> Thank you, Helmut!
>
> I've now requested an async resolution on your proposed clarification of 
> the spec regarding animation and transition behavior.
>
> Sebastian
>
> On Mon, 14 Sept 2026 at 21:18, Helmut Januschka <[email protected]> 
> wrote:
>
>> animation support has now landed:
>> https://chromium-review.googlesource.com/c/chromium/src/+/8277832
>>
>> This implements the CSSWG resolution: auto remains auto, resolves to the 
>> UA-chosen length when interpolated with a length, and auto-to-auto 
>> remains auto. WPT coverage is included.
>>
>> The remaining CSSWG work is to clarify the detailed animation and 
>> transition behavior in the specification:
>> https://github.com/w3c/csswg-drafts/issues/13036#issuecomment-5456514408
>>
>> Chromium and Firefox currently behave consistently for these cases. With 
>> the animation CL landed, is everyone fine with proceeding to default-on it?
>>
>> sorry that it took so long, and thanks for the guidance!
>>
>> cheers
>> Chris Harrelson schrieb am Mittwoch, 26. August 2026 um 17:16:57 UTC+2:
>>
>>> LGTM3, conditioned on landing animation support before shipping.
>>>
>>> On Wed, Aug 26, 2026 at 8:14 AM Vladimir Levin <[email protected]> 
>>> wrote:
>>>
>>>> LGTM2
>>>>
>>>> On Wednesday, August 26, 2026 at 11:11:06 AM UTC-4 Mike Taylor wrote:
>>>>
>>>>> Thanks Helmut.
>>>>>
>>>>> LGTM1 to ship, assuming we land animation support.
>>>>> On 8/25/26 1:36 p.m., Helmut Januschka wrote:
>>>>>
>>>>> @mike: feature entry updated and  the missing WPT is addressed as a 
>>>>> follow up in in: 
>>>>> https://chromium-review.googlesource.com/c/chromium/src/+/8277832 (in 
>>>>> review) 
>>>>>
>>>>> [email protected] schrieb am Dienstag, 25. August 2026 um 02:16:32 
>>>>> UTC+2:
>>>>>
>>>>>> On 8/24/26 5:54 p.m., Helmut Januschka wrote:
>>>>>>
>>>>>> @sebastian, thanks for the input.
>>>>>>
>>>>>> Yes, thanks Sebastian! 
>>>>>>
>>>>>> Helmut, do you mind updating the Chromestatus entry to reflected 
>>>>>> Shipped/Shipping, perhaps adding a Note about percentages?
>>>>>>
>>>>>>
>>>>>> @mike, sorry it was my fault for sure it works on all blink 
>>>>>> platforms, i just messed up the checkbox, allthough i went through all 
>>>>>> fields multiple times - i'll do better next time :/ 
>>>>>>
>>>>>> No worries - very simple mistake, and easy to fix. :)
>>>>>>
>>>>>> One question on WPTs: do we expect the failures at 
>>>>>> https://wpt.fyi/results/css/css-animations/text-decoration-inset-auto.html
>>>>>> ?
>>>>>>
>>>>>> (I think the rest of the tests are at 
>>>>>> https://wpt.fyi/results/css/css-text-decor?label=master&label=experimental&aligned&q=text-decoration-inset
>>>>>>  - 
>>>>>> which looks good)
>>>>>>
>>>>>>
>>>>>> [email protected] schrieb am Montag, 24. August 2026 um 22:40:16 
>>>>>> UTC+2:
>>>>>>
>>>>>>> On Monday, August 24, 2026 at 3:35:38 PM UTC+2 [email protected] 
>>>>>>> wrote:
>>>>>>>
>>>>>>> On 8/23/26 9:43 a.m., Helmut Januschka wrote:
>>>>>>>
>>>>>>> *Contact emails*
>>>>>>> [email protected]
>>>>>>>
>>>>>>> *Specification*
>>>>>>>
>>>>>>> https://drafts.csswg.org/css-text-decor-4/#propdef-text-decoration-inset
>>>>>>>
>>>>>>> *Summary*
>>>>>>> CSS text-decoration-inset controls how far underlines, overlines, 
>>>>>>> and line-through decorations are inset from or extended beyond text run 
>>>>>>> edges. It supports auto, length, and percentage values, including 
>>>>>>> one-value 
>>>>>>> and two-value syntax for setting the start and end offsets. This lets 
>>>>>>> developers adjust decoration spacing and create reveal effects with 
>>>>>>> native 
>>>>>>> text decorations instead of background gradients or additional 
>>>>>>> elements.  
>>>>>>>
>>>>>>> sampler: https://static.januschka.com/i-468928416/?asddsaasd  
>>>>>>>
>>>>>>>
>>>>>>> MDN: 
>>>>>>> https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/text-decoration-inset
>>>>>>>  
>>>>>>>
>>>>>>> CL: 
>>>>>>> https://chromium-review.googlesource.com/c/chromium/src/+/7748204
>>>>>>>
>>>>>>> *Blink component*
>>>>>>> Blink>CSS 
>>>>>>> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ECSS%22>
>>>>>>>
>>>>>>> *Web Feature ID*
>>>>>>> text-decoration <https://webstatus.dev/features/text-decoration>
>>>>>>>
>>>>>>> *Motivation*
>>>>>>> This change implements CSS text-decoration-inset (CSS Text 
>>>>>>> Decoration Level 4), including percentage values. It gives authors 
>>>>>>> direct 
>>>>>>> control over decoration inset and reduces the need for 
>>>>>>> wrapper/pseudo-element workarounds used to fine-tune 
>>>>>>> underline/overline/line-through rendering. 
>>>>>>>
>>>>>>>
>>>>>>> *Initial public proposal*
>>>>>>> *No information provided*
>>>>>>>
>>>>>>> *TAG review*
>>>>>>> *No information provided*
>>>>>>>
>>>>>>> *TAG review status*
>>>>>>> Not applicable
>>>>>>>
>>>>>>> *Goals for experimentation*
>>>>>>> None
>>>>>>>
>>>>>>> *Risks*
>>>>>>>
>>>>>>>
>>>>>>> *Interoperability and Compatibility*
>>>>>>> *No information provided*
>>>>>>>
>>>>>>> *Gecko*: No signal
>>>>>>>
>>>>>>> *WebKit*: No signal
>>>>>>>
>>>>>>> Can we please request signals?
>>>>>>>
>>>>>>>
>>>>>>> Mozilla has already shipped support for text-decoration-inset in 
>>>>>>> Firefox 146, see 
>>>>>>> https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/146#css,
>>>>>>>  
>>>>>>> though they are currently still working on support for percentages.
>>>>>>> Safari also recently implemented it in 
>>>>>>> https://bugs.webkit.org/show_bug.cgi?id=319178, see also 
>>>>>>> https://webkit.org/css-status/?#property-text-decoration-inset 
>>>>>>> <https://webkit.org/css-status/#property-text-decoration-inset>. 
>>>>>>> Though, as far as I could see, they are also currently lacking support 
>>>>>>> for 
>>>>>>> percentages, so I just filed 
>>>>>>> https://bugs.webkit.org/show_bug.cgi?id=322441 for that.
>>>>>>> Neither Apple nor Mozilla published standards positions for that 
>>>>>>> feature, though.
>>>>>>>
>>>>>>> Sebastian
>>>>>>>
>>>>>> -- 
>>>>
>>> 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/f1821795-e9f8-4a22-bdb0-00a7b50b23ddn%40chromium.org
>>>>  
>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/f1821795-e9f8-4a22-bdb0-00a7b50b23ddn%40chromium.org?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/da681315-8ae7-49c7-8e99-4d3d44ef72c1n%40chromium.org.

Reply via email to