[prev in list] [next in list] [prev in thread] [next in thread] 

List:       whatwg
Subject:    Re: [whatwg] Questions regarding Path object
From:       Jürg_Lehni <lists () scratchdisk ! com>
Date:       2013-06-24 22:41:06
Message-ID: 6460FCFE-051B-4610-AFA3-69A3EC847958 () scratchdisk ! com
[Download RAW message or body]

Well I know there will be problems: Paper.js has a Path class since 2011, and these \
will clash when using the library without scoping, which is what many people do.

I was hoping that a more specific name could be adopted before the standard is set in \
stone, hence the proposal of adding 2D to all global constructors that relate to 2D \
graphics and canvas.

I doubt we're the only library that clashes.

Jürg

On Jun 24, 2013, at 08:55 , Dirk Schulze <dschulze@adobe.com> wrote:

> 
> On Jun 24, 2013, at 8:38 AM, Jürg Lehni <lists@scratchdisk.com> wrote:
> 
> > On Jun 17, 2013, at 17:55 , Rik Cabanier <cabanier@gmail.com> wrote:
> > 
> > > I think we need to get some browser vendors on board. 
> > 
> > What's the process to do so?
> > 
> > > However, I believe Firefox has been working on landing 'path' and there was a \
> > > patch for WebKit that also landed a partial path object. I'm unsure if these \
> > > ended up in shipping browsers.
> > 
> > Would that mean it's too late? I really hope not!
> 
> You can check if you see problems in WebKit nightlies or in Chrome/Chromium with \
> the experimental flag enabled. 
> Greetings,
> Dirk
> 
> > 
> > Best,
> > 
> > Jürg
> 


[prev in list] [next in list] [prev in thread] [next in thread]