I know of at least one JS library that uses Path as object (paper.js). But the definition can be overridden. It is unlikely that this will break content, as long as the library does not want to use both. Other then that, the SVG WG wants to reuse the Path object in SVG and CanvasObject might confuse people but this seems unlikely as well.
Greetings, Dirk Sent from my iPhone On Sep 23, 2012, at 6:22 AM, "Elliott Sprehn" <espr...@chromium.org<mailto:espr...@chromium.org>> wrote: On Fri, Sep 21, 2012 at 6:34 AM, Dirk Schulze <dschu...@adobe.com<mailto:dschu...@adobe.com>> wrote: Hi WebKit, I would like to ask if there are objections to implement the canvas Path object. Do we have metrics on how often people already have things named Path? All other canvas objects have a prefix like CanvasGradient and CanvasPattern, this thing seems inconsistent and more likely to break existing pages. - E
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
