- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Fri, 24 Oct 2025 02:35:35 +0000
- To: public-css-archive@w3.org
tabatkins has just submitted a new pull request for https://github.com/w3c/csswg-drafts: == Add the proposed syntax stuff from the f2f discussion == This relates to the following: * [#12652](https://github.com/w3c/csswg-drafts/issues/12652#issuecomment-3329841437) animation-trigger CSS Syntax * [#12611](https://github.com/w3c/csswg-drafts/issues/12611#issuecomment-3382276301) Set of actions for AnimationTrigger * [#12336](https://github.com/w3c/csswg-drafts/issues/12336#issuecomment-3206545734) Move scroll and event animation triggers to independent namespace * [#12581](https://github.com/w3c/csswg-drafts/issues/12581#issuecomment-3206707173) animation-trigger name clash resolution * [#12399](https://github.com/w3c/csswg-drafts/issues/12399) Should an animation be allowed to have multiple triggers associated? (Resolution says only one trigger per animation right now, but I went ahead and did multiple with the proposed syntax in the issue, since other convos settled us on a usable syntax for this.) This does not handle the OM side of things yet, as the point of this is just to give us a single thing to look at when getting final approval, rather than scattered decisions across multiple issues. See https://github.com/w3c/csswg-drafts/pull/13009 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 24 October 2025 02:35:36 UTC