W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2013

Re: [whatwg] Questions regarding Path object

From: Dean Jackson <dino@apple.com>
Date: Sat, 19 Oct 2013 06:06:02 +1100
Message-id: <03834388-E3FC-4292-B3E1-DA62E9E6500D@apple.com>
To: Ian Hickson <ian@hixie.ch>
Cc: Juriy Zaytsev <kangax@gmail.com>, Rik Cabanier <cabanier@gmail.com>, Jürg Lehni <lists@scratchdisk.com>, "whatwg@lists.whatwg.org" <whatwg@lists.whatwg.org>, Simon Pieters <simonp@opera.com>, Dirk Schulze <dschulze@adobe.com>

On 17 Oct 2013, at 9:20 am, Ian Hickson <ian@hixie.ch> wrote:

>> PS: iOS 7 is barely released, but the first bug reports are already 
>> coming in, because the new Mobile Safari now defines Path, and clashes:
>> https://twitter.com/danetag/status/380636739251220480
> Looks like this user solved the problem pretty quickly.
> I tried to find more evidence of problems now that iOS7 is out with this, 
> but I'm not finding much. (I did a bunch of searches on Google.) 
> Having said that, I'm not saying there's no conflicts. If Chrome and 
> Safari want to change to a different name, we can definitely still do 
> that, it's early days yet. DOMPath, maybe? Or Path2D, or CanvasPath.
> Still, on the long term it'd be sad that we can't just use Path.

FWIW, many new specifications are hitting issues like this (well…
at least Web Animations!). It’s a pain that new classes can
clash with existing content, but I think we have to act
as if the future is bigger than the past and thus pick the best
name for the job.

As someone else said, the rule of not injecting into the global
namespace from a JS library has been known for a few years now,
and if you’re still not doing it you’re asking for trouble.

Received on Friday, 18 October 2013 19:06:46 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:12 UTC