[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] Help with the WebGL Context Lost specification
Thank you for helping with this.
On Sun, Nov 13, 2011 at 8:16 AM, Glenn Maynard <email@example.com>
On Sat, Nov 12, 2011 at 12:59 PM, Glenn Maynard <firstname.lastname@example.org>
The "interrupting" nature of losing a context is something that most web
APIs are very careful to never allow.
Thinking about this some more, this can be done without having to "interrupt" JS code or change things asynchronously, by defining context loss as happening only 1: as a queued task or 2: when a WebGL call is made on the context. That's probably what happens with real implementations, anyway. If this sounds reasonable, I'll try to write some language for this.
The context can be lost at any time but you're right, from the POV of JS it won't notice any thing unless it calls WebGL (or gets the event)