Re: [fxtf-drafts] [motion-1] "equivalent path" mismatches between SVG and Motion (#506)

After doing some more archaeology, it seems clear that only path() was actually desired for offset-path; the rest of the basic-shapes came in because we want to consistently handle all the path-ish things the same way for anything that takes any of them.

So I'm going to assume, absent any data, that there's no real usage to worry about here, and I can go ahead and change the equivalent path to match SVG.

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


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

Received on Tuesday, 7 March 2023 20:44:15 UTC