Daniil Sakhapov via GitHub
- [fxtf-drafts] [motion-1] Make offset-position more specific (#499)
- [fxtf-drafts] [motion-1] Explicit reference box for basic shapes (#498)
- [fxtf-drafts] Pull Request: [motion-1] Move path() to the <basic-shape> section.
- [fxtf-drafts] Pull Request: [motion-1] Make <ray-size> optional. Defaulting to 'closest-side'.
- [fxtf-drafts] [motion-1] <path> is now one of the <basic-shape> (#493)
- [fxtf-drafts] [motion-1] Ray examples are not correct (#492)
- [fxtf-drafts] [motion-1] Make <size> of ray function optional (#491)
dontcallmedom-bot via GitHub
Guillaume via GitHub
- Re: [fxtf-drafts] [motion-1] <path> is now one of the <basic-shape> (#493)
- Re: [fxtf-drafts] [motion-1] Incorrect type definition link in <size> (#411)
- [fxtf-drafts] [compositing-2] Define properties with animation type (#497)
- [fxtf-drafts] [filter-effects-2] Define `backdrop-filter` with animation type (#496)
Tab Atkins Jr. via GitHub
- Closed: [fxtf-drafts] [motion-1] Make <size> of ray function optional (#491)
- Closed: [fxtf-drafts] [motion-1] <path> is now one of the <basic-shape> (#493)
- Closed: [fxtf-drafts] [motion-1] Incorrect type definition link in <size> (#411)
- Re: [fxtf-drafts] [motion-1] the description of contain flag in ray() function (#363)
- Re: [fxtf-drafts] [motion-1] Ray examples are not correct (#492)
- Re: [fxtf-drafts] [motion-1] <path> is now one of the <basic-shape> (#493)
- Re: [fxtf-drafts] [motion-1] Make <size> of ray function optional (#491)
- Re: [fxtf-drafts] [motion-1] the description of contain flag in ray() function (#363)