Re: [Public WebGL] Re: [whatwg] Canvas.getContext error handling

Subject: Re: [Public WebGL] Re: [whatwg] Canvas.getContext error handling

From: Glenn Maynard <glenn@zewt.org>

Date: Mon, 25 Apr 2011 00:45:44 -0400

Cc: Kenneth Russell <kbr@google.com>, Mark Callow <callow_mark@hicorp.co.jp>, public_webgl@khronos.org

In-reply-to: <BANLkTikNLiKt=YA5+5OjgYvh0-tC-p2B2A@mail.gmail.com>

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

References: <BANLkTimo3JXAjxHPMNW-Az6-A47LjP6gNw@mail.gmail.com> <BANLkTimGSvfuk36Qja+S=NdUCcxXoO-NVg@mail.gmail.com> <BANLkTintm6cjrDorYJnNJ+XP-c8mWH8hYQ@mail.gmail.com> <Pine.LNX.4.64.1104120704360.25791@ps20323.dreamhostps.com> <4DA4198A.2080006@mit.edu> <BANLkTi=RRBpCL8PV48C1f44AEtfNFavpnw@mail.gmail.com> <BANLkTi=YM_fq=T2MRBEtbwZ+h8xzPjZ5-g@mail.gmail.com> <BANLkTimmgyDUMX0eXqdTf47EHs+LZ66TWA@mail.gmail.com> <BANLkTinBz6-D8BSUssTrqiWjewiPedWEnw@mail.gmail.com> <BANLkTikMN-0TREAWsL3ROMP=XY3xzMAEAA@mail.gmail.com> <BANLkTimFVVJNgohfHmbuXrRp5O3By79APQ@mail.gmail.com> <BANLkTi=KDmpYrWWHp2SuKB5MRtVCTggq8Q@mail.gmail.com> <4DAE42F7.1000202@hicorp.co.jp> <BANLkTinp2r+tjCWV1w_DnA-Je3wQSr94LQ@mail.gmail.com> <BANLkTi=vZmAF1PqBfrqXpW0yYD_2+cUGkw@mail.gmail.com> <BANLkTimmpMSZ_d0Q01QX5Ph6J+zcqdAd4g@mail.gmail.com> <BANLkTikNLiKt=YA5+5OjgYvh0-tC-p2B2A@mail.gmail.com>

Sender: owner-public_webgl@khronos.org

On Mon, Apr 25, 2011 at 12:31 AM, Cedric Vivier <cvivier@mozilla.com> wrote:

On Sun, Apr 24, 2011 at 00:42, Glenn Maynard <glenn@zewt.org> wrote:
>> Additionally, if we proceed with this change, I do not support the
>> removal of the statusMessage. As an implementor of WebGL, I require
>> the ability to provide some information to application developers
>> (which might end up being sent back in in bug reports) when for some
>> reason WebGL could not initialize.
>
> My suggestion was to include the statusMessage within webglcontextlost.

statusMessage is already present in the WebGLContextEvent object all
WebGL-initiated events share.

Yes, but in webglcontextlost it's currently empty.

My proposal is to add a boolean flag to know whether a context loss is
permanent or not, as Mark and I pointed out, having to parse a
(possibly localized) string to check this simple boolean status is
error-prone and confusing at best.

You're replying to something unrelated--I already agreed that the flag should be there.