- From: Boris Chiou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 May 2023 22:58:09 +0000
- To: public-fxtf-archive@w3.org
BorisChiou has just created a new issue for https://github.com/w3c/fxtf-drafts: == [motion-1] <fill-rule> in path() function == Per the current spec, [the definition of `offset-path`](https://drafts.fxtf.org/motion-1/#offset-path-property) is `none | <offset-path> || <coord-box>`. And `<offset-path>` could be `<ray>`, `<url>`, `<basic-shape>`. [The syntax of `path()` in `<basic-shape>`](https://drafts.csswg.org/css-shapes-1/#funcdef-basic-shape-path) is `path([<fill-rule>]? [<string>])`. `<fill-rule>` is useful only for clip-path and shape-outside. For motion, we didn't have `<fill-rule>` in the spec before (at least when I worked on this 4 years ago). However, now we use `<basic-shape>` to include all kinds of shapes. So perhaps it's worth to note that `<fill-rule>` is ignored and we don't have to serialize it even if the users specify it? Or should we still serialize it if it is not the default value? Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/512 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 10 May 2023 22:58:11 UTC