- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Mar 2018 22:41:39 +0000
- To: public-svg-issues@w3.org
I agree that, for consistency, the new attributes should be reflected in properties. That said, it's not straightforward how to do so. For `side`, do we create new named constants to expose it as an `SVGAnimatedEnumeration`, or expose it as a modern WebIDL enum? (Since there are already two other enumerations on the class, I'd sadly have to vote for using something `const unsigned short TEXTPATH_SIDE_LEFT= 1`) For `path`, there is no standard way of exposing path data as DOM properties in SVG 2. The `d` property is not exposed on `SVGPathElement`. The SVG 1 interfaces to path data were removed, and the replacements are languishing in the [Paths module](https://svgwg.org/specs/paths/#DOMInterfaces). (But, that said, you'd have to dig through the old www-svg discussions to confirm whether there was an intentional decision not to expose these attributes as DOM properties, or if it was just an oversight.) -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/issues/391#issuecomment-373199268 using your GitHub account
Received on Wednesday, 14 March 2018 22:41:42 UTC