Listening for context lost events on the context itself seems like the
best and most correct solution. If that's supported, would
DrawingBuffer need to support them? I don't think so.
Web workers seem to be able to actually listen for events (see the
onconnect message in
http://www.whatwg.org/specs/web-apps/current-work/multipage/workers.html#handler-sharedworkerglobalscope-onconnect
), so hopefully adding an event handling mechanism to
WebGLRenderingContext would not cause any issues with using WebGL in
workers.
-Ken
On Fri, Feb 22, 2013 at 2:31 PM, Gregg Tavares <gman@google.com> wrote:
>
>
>
> On Fri, Feb 22, 2013 at 5:00 AM, Florian Bösch <pyalot@gmail.com> wrote:
>>
>> I just noticed that the context loss events are registered on the canvas
>> rather than the context.
>>
>>
>> The newly proposed functionality of canvas independent contexts would make
>> it awkward to handle context losses (you will have to register the event on
>> every conceivable canvas and check that you don't double handle it).
>>
>> Would it be appropriate to extend the WebGLContext object with an event
>> handling mechanism so it can be handled per context?
>
>
> Yes, good point. They might need to be on DrawingBuffer too if we go that
> route.
>
>