Re: [Public WebGL] Firefox 4 and blacklist reporting

To: Mark Callow <callow_mark@hicorp.co.jp>

Subject: Re: [Public WebGL] Firefox 4 and blacklist reporting

From: Arthur Blume <arthurb@google.com>

Date: Tue, 29 Mar 2011 07:08:08 -0400

Cc: Kenneth Russell <kbr@google.com>, Benoit Jacob <bjacob@mozilla.com>, public webgl <public_webgl@khronos.org>

Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1301398145; bh=J8xH5dhXYpvwiL9dyiQ7eawaGxs=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=Cb6F58iFma1gn/bPlq92Ph6dFZLGed3fgGDY2ir5pyPga0flYLQzmdr2lt8NWQzAl slQPb3gJnw4bg40N7L8+g==

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=aq9XGo3awQ9uoY2CclfE2QR0OXNqrOcZwCXgbhTeFig=; b=WLoINOEOSh1UJ5fFEWFQz9Zq4CTwV1qAxS81xokuFoTb1ADWXnaxQa5265dwTn0qkO 0XM+Fewn6LVyf4TwdFSg==

Domainkey-signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=UlBvBqtvwRxy3VbKWVemwFIgkJveoN5lpgoghcY3rqgAKofRTvZuB///J9kpe3ZIZB bk38Y7EJ2zI45zAAJnMg==

In-reply-to: <4D919853.50101@hicorp.co.jp>

List-id: Public WebGL Mailing List <public_webgl.khronos.org>

References: <BANLkTi=0UkhHOwpZTzLaXhYTa_L9ZSG6xg@mail.gmail.com> <2076227978.75895.1301336325818.JavaMail.root@cm-mail03.mozilla.org> <BANLkTimpw8Gp9BXbz7h2WAaqQt9qGBrjKQ@mail.gmail.com> <4D919853.50101@hicorp.co.jp>

Sender: owner-public_webgl@khronos.org

We'll keep our special case exception checking code for current FF4, but we'll also have a handler for webglcontextcreationerror.

I have a follow-up question but I'll ask it in another thread.

On Tue, Mar 29, 2011 at 4:29 AM, Mark Callow <callow_mark@hicorp.co.jp> wrote:

On 29/03/2011 03:57, Kenneth Russell wrote:
> The spec says that getContext() is supposed to return null, not throw
> an exception, and report a webglcontextcreationerror. See
> http://www.khronos.org/registry/webgl/specs/latest/#5.14.3 .

Neither the FAQ nor webgl-utils.js on the public wiki provide any
information about how to handle this error. In fact webgl-utils.js
recommends sending the user to get.webgl.org/troubleshooting in the case
that getContext() returns null.

I thought get.webgl.org/troubleshooting would try the context creation
again and display the error string from webglcontextcreationerror, if
any? From my test it appears not. When I tried from Chrome on a machine
with a blacklisted GPU troubleshooting tells me

"Click here for WebGL troubleshooting info for Chrome on Windows"

When I click that I get a error page telling me the page is unavailable.

In summary, the FAQ needs to show how to handle the error and
get.webgl.org/troubleshooting needs to use it and display any message
from the browser.

Regards

-Mark