public-fxtf-archive@w3.org from February 2023 by thread

Closed: [fxtf-drafts] [motion-1] Incorrect type definition link in <size> (#411) Tab Atkins Jr. via GitHub (Tuesday, 21 February)

[fxtf-drafts] [motion-1] Make offset-position more specific (#499) Daniil Sakhapov via GitHub (Wednesday, 8 February)

[fxtf-drafts] [motion-1] Explicit reference box for basic shapes (#498) Daniil Sakhapov via GitHub (Wednesday, 8 February)

Re: [fxtf-drafts] [motion-1] Incorrect type definition link in <size> (#411) Guillaume via GitHub (Wednesday, 8 February)

[fxtf-drafts] [compositing-2] Define properties with animation type (#497) Guillaume via GitHub (Wednesday, 8 February)

[fxtf-drafts] [filter-effects-2] Define `backdrop-filter` with animation type (#496) Guillaume via GitHub (Wednesday, 8 February)

[fxtf-drafts] Pull Request: [motion-1] Move path() to the <basic-shape> section. Daniil Sakhapov via GitHub (Wednesday, 8 February)

[fxtf-drafts] Pull Request: [motion-1] Make <ray-size> optional. Defaulting to 'closest-side'. Daniil Sakhapov via GitHub (Wednesday, 8 February)

Re: [fxtf-drafts] [motion-1] the description of contain flag in ray() function (#363) Tab Atkins Jr. via GitHub (Monday, 6 February)

[fxtf-drafts] [motion-1] <path> is now one of the <basic-shape> (#493) Daniil Sakhapov via GitHub (Monday, 6 February)

[fxtf-drafts] [motion-1] Ray examples are not correct (#492) Daniil Sakhapov via GitHub (Monday, 6 February)

[fxtf-drafts] [motion-1] Make <size> of ray function optional (#491) Daniil Sakhapov via GitHub (Monday, 6 February)

[fxtf-drafts] [compositing-2] Broken references in Compositing and Blending Level 2 (#490) dontcallmedom-bot via GitHub (Thursday, 2 February)

Last message date: Tuesday, 28 February 2023 05:40:14 UTC