[whatwg] Questions regarding Path object

[Ian Hickson]

On Mon, 11 Nov 2013, Elliott Sprehn wrote:
> 
> Then I object to us shipping this in Chrome. Bleeding on the global 
> scope with such a generic name ignoring all the other reasonable uses of 
> the word Path is not good for the platform. It's not forward thinking, 
> and it's confusing for developers.

The name issue was raised before (the name clashes with the paper.js 
library, IIRC), but no vendor had objected (the feature was added over a 
year ago now - March 2012), the suggested alternative names weren't great, 
the compatibility issue wasn't huge, and so I left it as is, and Apple 
shipped it. Changing it now seems like a poor time to change it.

...but, if you won't ship it, maybe we need to change it after all? Would 
Apple ship a different name? What are Mozilla's opinions?

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'