- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Dec 2023 10:34:41 +0000
- To: public-css-archive@w3.org
In order to close this issue, it seems that defining how to handle `<'fill-rule'>` in some contexts still needs to be defined. People may be confused without a clarification in the related specs for these contexts (see https://github.com/w3c/fxtf-drafts/issues/512 and #7390), now that `path()` and `polygon()` are defined to accept an optional `<'fill-rule'>` in CSS Shapes, whose default value is `nonzero` instead of `evenodd`, as noted in the above resolution, which I assume is intentional. If I am not mistaken, it boils down to defining that: - `<'fill-rule'>` must be ignored and omitted in the serialization when the context is `offset-path` ([Motion 1](https://drafts.fxtf.org/motion-1/#valdef-offset-path-basic-shape)) - `<'fill-rule'>` must take precedence over `fill-rule` and `clip-rule` when the context is `d` ([SVG 2](https://svgwg.org/svg2-draft/paths.html#DProperty)), assuming its value definition is `none | <path()>` (as currently implemented in browsers) instead of `none | <string>` -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3468#issuecomment-1864239057 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 December 2023 10:34:43 UTC