Re: [svgwg] 'd' presentation attribute: use path() function

@ewilligers The change you made affects the `d` property _as well_ as the `d` presentation attribute. So you pretty much disallow path strings everywhere. This is the compatibility issue I mean. Furthermore, it is confusing that one will be allowed to use path strings on the `d` presentation attribute but not on the `d` CSS property. You can't simply copy the content from the attribute to the style section and are done with it. You must add the `path()` function. IMO there is no benefit to not allow the path string even if it is for the `d` property only. We are not getting away with the path string on the `d` presentation attribute ever. So why forcing its removal on the CSS property?

Also, the spec text should say what happens when a `<fill-rule>` was specified. How does this interact with the `fill-rule` CSS property? CSS Masking has a similar problem with `clip-rule` and `clip-path`.

@AmeliaBR I totally agree with you. IMO it is fine that Chrome starts shipping with `path()` and adds support for other shapes later but spec wise we should not split the shape functions.

IMO we should not make this change for SVG2 at all and instead split the `d` property out in general into its own spec or another existing FXTF/CSSWG spec. The path data string logic can stay in SVG2 for now.

-- 
GitHub Notification of comment by dirkschulze
Please view or discuss this issue at https://github.com/w3c/svgwg/pull/374#issuecomment-355888380 using your GitHub account

Received on Monday, 8 January 2018 05:52:13 UTC