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

Re: [whatwg] Challenging canvas.supportsContext

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 19 Jun 2013 14:26:57 -0700
Message-ID: <CAAWBYDCTShtyUFWZ=GfKJgtGYp0H34CJd+frH2Fn4eT_xaqCTw@mail.gmail.com>
To: Brandon Benvie <bbenvie@mozilla.com>
Cc: whatwg <whatwg@lists.whatwg.org>, James Robinson <jamesr@google.com>
On Wed, Jun 19, 2013 at 2:20 PM, Brandon Benvie <bbenvie@mozilla.com> wrote:
> On 6/19/2013 2:05 PM, James Robinson wrote:
>> I'm also failing to see the utility of the supportsContext() call.  It's
>> impossible for a browser to promise that supportsContext('webgl') implies
>> that getContext('webgl') will succeed without doing all of the expensive
>> work, so any correctly authored page will have to handle a
>> getContext('webgl') failure anyway.
>
> Given this, it would seem supportsContext is completely useless. The whole
> purpose of a feature detection check is to detect if a feature actually
> works or not. Accuracy is more important than cost.

Hmm, I guess I agree.  That sucks, but you're right - it's much more
important that you *actually* be able to generate a context when the
feature-detect says you can.

~TJ
Received on Wednesday, 19 June 2013 21:27:42 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:22 UTC