Re: [fxtf-drafts] [motion-1] Initial position of a path() (#505)

Letting `shape()` cover this use-case is also OK to me, so we don't have to change anything to `path()` (e.g. add `at <position>` to its syntax).

> Do we want to distinguish between a path that has an explicitly given initial move-to, and let ones without such a move-to use the 'offset-position' as their initial position?

Per SVG1 (https://www.w3.org/TR/SVG11/paths.html#PathDataBNF), and SVG2 (https://www.w3.org/TR/SVG/paths.html#PathDataBNF), it seems the syntax of svg path should always have the initial `move_to` command.

So I expect `path()` should always specify the initial position, by the initial `move_to` command. That means it should be fine to let `path()` just ignore `offset-position` because the initial position should always be there, per its syntax. (This may be the same as `url()` because I expect the SVG element always provide the initial position.)

-- 
GitHub Notification of comment by BorisChiou
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/505#issuecomment-1678248747 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 15 August 2023 00:03:11 UTC