This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#path-objects Complete: http://www.whatwg.org/c#path-objects Referrer: Comment: Path objects would be much more useful if their individual commands (moveTo, lineTo, etc.) could be inspected from JavaScript. This would allow for the JavaScript implementation of missing features such as text-to-path conversion, boolean shape operations, custom transforms (e.g. perspective), custom stroke styles, and so on. Posted from: 173.228.28.163 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.73 Safari/537.36
Yeah, that's an obvious next step. One day.
One problem with this is that it requires that we define exactly what the representation is, when it would otherwise need to be an approximation. Consider the path constructed out of text, or the path constructed out of stroking another path that contains a bezier curve.
If this is still desired, please file a new issue at https://github.com/whatwg/html/issues/new.