- From: Florian Rivoal via GitHub <noreply@w3.org>
- Date: Wed, 16 Jul 2025 17:26:40 +0000
- To: public-css-archive@w3.org
In summary:
1. `blink` doesn't do anything beyond parsing in any browser
2. currently, Firefox takes `underline blink` and computes to / inherits as `underline blink`, while Chrome and Safari simplify it to just `underline`:
https://software.hixie.ch/utilities/js/live-dom-viewer/?saved=13926
3. This simplification is happening at computed value time, because all three browsers preserve `underline blink` in the specified value:
https://software.hixie.ch/utilities/js/live-dom-viewer/?saved=13927
Currently, the definition of `blink` is this: https://drafts.csswg.org/css-text-decor-4/#valdef-text-decoration-line-blink
> The text blinks (alternates between visible and invisible). Conforming user agents may simply not blink the text. Note that not blinking the text is one technique to satisfy [checkpoint 3.3 of WAI-UAAG](https://www.w3.org/TR/UAAG/guidelines.html#tech-on-off-blinking-text). This value is deprecated in favor of Animations [[CSS3-ANIMATIONS]](https://drafts.csswg.org/css-text-decor-4/#biblio-css3-animations).
If we want the Firefox behavior, The definition of the blink keyword could be something like:
> This legacy value must be supported for parsing purposes, but has no effect.
If we want the Chrome/Safari behavior, we might expand it to with something like:
> This legacy value must be supported for parsing purposes, but has no effect.
> If specified alone, the `blink` keyword computes to `none`.
> If specified in combination with one or more other keywords, the `blink` keyword is dropped from the computed value.
--
GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12015#issuecomment-3079559254 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 July 2025 17:26:41 UTC