- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 Jan 2018 01:44:20 +0000
- To: public-svg-issues@w3.org
@dirkschulze For reference, there is discussion in the following issues: - https://github.com/w3c/svgwg/issues/49 - https://github.com/w3c/svgwg/issues/119 - https://github.com/w3c/svgwg/issues/320 I still strongly disagree with using `path()` in any place other than as an interoperable `<shape-function>` where it can be substituted for any of the other shape functions. But none of the other implementers have weighed in to argue for that approach, and Chrome has been shipping it following Eric's proposal. I will point out that the current state (`path()` supported in some CSS properties, other shapes in other properties) has proven to be very confusing to authors: https://css-tricks.com/basic-shapes-path-never-twain-shall-meet/ The proposal should probably be discussed with CSS WG as well as SVG. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/pull/374#issuecomment-355870760 using your GitHub account
Received on Monday, 8 January 2018 01:44:23 UTC