- From: Travis Leithead <travis.leithead@microsoft.com>
- Date: Tue, 11 Sep 2012 16:37:04 +0000
- To: Robin Berjon <robin@w3.org>, Dean Jackson <dino@apple.com>
- CC: "public-html@w3.org" <public-html@w3.org>
Hmm. Seems like this still incurs the cost of spinning up a context. Never mind :(
> -----Original Message-----
> From: Travis Leithead
> Sent: Tuesday, September 11, 2012 9:12 AM
> To: 'Robin Berjon'; Dean Jackson
> Cc: public-html@w3.org
> Subject: RE: [Canvas] proposal for supportsContext
>
> On the other hand, you could change the way that the 3d context is
> obtained from the canvas element, to better allow feature detection...
>
> if (canvas.context3d) {
> ...
> }
>
> ??
>
> > -----Original Message-----
> > From: Robin Berjon [mailto:robin@w3.org]
> > Sent: Tuesday, September 11, 2012 1:41 AM
> > To: Dean Jackson
> > Cc: public-html@w3.org
> > Subject: Re: [Canvas] proposal for supportsContext
> >
> > Hi Dean,
> >
> > On 10/09/2012 20:11 , Dean Jackson wrote:
> > > I propose adding a new method to HTMLCanvasElement:
> > >
> > > interface HTMLCanvasElement : HTMLElement {
> > > boolean supportsContext(DOMString contextId, any... arguments);
> > > };
> > >
> > > supportsContext takes the same parameters as getContext, and simply
> > returns
> > > true if the corresponding call to getContext would have returned a
> valid
> > > context, false otherwise.
> >
> > I like it. My only concern is about why this would work when
> > hasFeature() failed so miserably. I guess that it covers a sufficiently
> > limited set that it will be done right.
> >
> > --
> > Robin Berjon - http://berjon.com/ - @robinberjon
> >
Received on Tuesday, 11 September 2012 16:37:42 UTC