- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 18 Mar 2025 17:00:36 +0000
- To: www-svg@w3.org
- Message-Id: <E1tuaIu-00CiEJ-0f@janus.w3.internal>
Events with label "SVG", "css-fill-and-stroke-3", "css-shapes-1", "css-shapes-2", "css-transforms-1", "css-transforms-2", "fx-filter-effects-1", "web-animations-1", "web-animations-2"
Issues
------
* w3c/csswg-drafts (+1/-1/đŸ’¬13)
1 issues created:
- [web-animations-1] The expected behavior when calling animate() on the removed element (by BorisChiou)
https://github.com/w3c/csswg-drafts/issues/11950 [web-animations-1]
8 issues received 13 new comments:
- #11950 [web-animations-1] The expected behavior when calling animate() on the removed element (2 by BorisChiou, birtles)
https://github.com/w3c/csswg-drafts/issues/11950 [web-animations-1]
- #11932 [web-animations-2][css-animations-2] How should unspecified trigger range boundaries be resolved? (3 by DavMila, ydaniv)
https://github.com/w3c/csswg-drafts/issues/11932 [css-animations-2] [web-animations-2]
- #11918 [web-animations-2] Should AnimationTrigger properties be readonly? (1 by ydaniv)
https://github.com/w3c/csswg-drafts/issues/11918 [web-animations-2]
- #11914 [web-animations-2]Should animation triggers have equal control over their animations’ playback? (1 by ydaniv)
https://github.com/w3c/csswg-drafts/issues/11914 [web-animations-2]
- #11910 [web-animations-2][css-animations-2] Should animation-trigger-exit-range be constrained to being as greater than or equal to animation-trigger-range? (1 by ydaniv)
https://github.com/w3c/csswg-drafts/issues/11910 [css-animations-2] [web-animations-2]
- #11611 [web-animations-2][css-animations-2] Allow controlling video playback via an animation timeline (1 by ydaniv)
https://github.com/w3c/csswg-drafts/issues/11611 [css-animations-2] [web-animations-2]
- #11054 [css-animations-2] interaction between the `timeline` property and `animation-timeline` property (3 by flackr, graouts, ydaniv)
https://github.com/w3c/csswg-drafts/issues/11054 [css-animations-2] [web-animations-2]
- #2070 [web-animations-2] Element.animate could allow keyframes to come from CSS declaration (1 by ydaniv)
https://github.com/w3c/csswg-drafts/issues/2070 [web-animations-2]
1 issues closed:
- [css-animations-2] interaction between the `timeline` property and `animation-timeline` property https://github.com/w3c/csswg-drafts/issues/11054 [css-animations-2] [web-animations-2]
Pull requests
-------------
* w3c/csswg-drafts (+1/-1/đŸ’¬1)
1 pull requests submitted:
- [web-animations-2] Editorial: fixed some bikeshed errors and warnings (by ydaniv)
https://github.com/w3c/csswg-drafts/pull/11944 [web-animations-2]
1 pull requests received 1 new comments:
- #11944 [web-animations-2] Editorial: fixed some bikeshed errors and warnings (1 by birtles)
https://github.com/w3c/csswg-drafts/pull/11944 [web-animations-2]
1 pull requests merged:
- [web-animations-2] Editorial: fixed some bikeshed errors and warnings
https://github.com/w3c/csswg-drafts/pull/11944 [web-animations-2]
Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/csswg-drafts
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 March 2025 17:00:38 UTC