As part of improving the SVG DOM, I think we should consider renaming SVGPathSegList to SVGPath (or perhaps even just Path). SVGPathSegList is unwieldy if we want to add a constructor to the interface so that authors can do var p = new SVGPath("M100,100 ..."); Does anyone think there would be any compatibility risk with this?Received on Friday, 21 October 2011 18:11:59 GMT
This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:49 GMT