- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Oct 2023 23:52:48 +0000
- To: public-fxtf-archive@w3.org
The CSS Working Group just discussed `[css-masking-1] Interpolation of mask-border properties`, and agreed to the following: * `RESOLVED: mask-border properties will match border-image wrt animatability` <details><summary>The full IRC log of that discussion</summary> <lea> 2nd Straw poll posted! https://github.com/w3c/csswg-drafts/issues/7542#issuecomment-1747805436<br> <fantasai> ntim: The properties are marked as discretely animatable, but that's inconsistent with border-image which is animatable by computed style<br> <fantasai> ntim: I know mask-border was based off border-image, so I was wondering why the inconsistency?<br> <TabAtkins> +1 to matching border-image<br> <TabAtkins> fantasai: I suspect (haven't checked) is that animatable lines weren't added in the source, and Bikeshed defaults them to discrete<br> <TabAtkins> fantasai: But yes it makes sense to make them consistent<br> <TabAtkins> (I could just make it an error at this point; that didn't make sense before.)<br> <fantasai> astearns: Proposed to change mask border properties to match border-image<br> <fantasai> RESOLVED: mask-border properties will match border-image wrt animatability<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/529#issuecomment-1747806968 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 4 October 2023 23:52:49 UTC