- From: Kevin Babbitt via GitHub <noreply@w3.org>
- Date: Wed, 18 Feb 2026 01:19:14 +0000
- To: public-css-archive@w3.org
I agree that for https://bug-307933-attachments.webkit.org/attachment.cgi?id=478391, the expected effect after the change to border computed value should be that a solid border pops in at 50% of the way through the transition, then shrinks to 0px over the rest of the duration. In Chrome Canary I don't see the border animate at all, which seems like a bug. Tagging in @oSamDavis who did the implementation in Chromium. In Firefox and Nightly I see the border pop in at the start of the transition rather than at 50%, but that's probably a separate issue. If this is a significant enough web compat issue that we want to address it, I would rather undo the decoupling change with respect to the border properties than special-case border-width to transition off of used values. -- GitHub Notification of comment by kbabbitt Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13511#issuecomment-3917934782 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 February 2026 01:19:15 UTC