- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Sat, 27 May 2017 15:38:58 +0000
- To: public-svg-issues@w3.org
There were extensive discussions about this, which no one from Blink participated in. See #49 and #119. The version shipped by Blink does not make sense & is inconsistent with other properties. The fact that it was shipped based on an early draft that was still being debated in the working group, with no experimental flag, is something that reflects poorly on Blink's implementation process. The `path()` function, as spec'd, is a `<shape-function>` data type that can be used and replaced in any context where `circle()`, `ellipse()`, `polygon()` and `inset()` are used. Furthermore, the `path()` function includes a fill-rule parameter, but the fill-rule for `<path>` elements is defined by a separate property. In contrast, `offset-path`, as spec'd, should accept any of the shape functions are valid. (The fill-rule isn't relevant, but it isn't a contradiction, either.) Last I checked, Blink's motion path implementation _only_ accepted path, but that is a limitation of the implementation. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/issues/320#issuecomment-304459488 using your GitHub account
Received on Saturday, 27 May 2017 15:39:06 UTC