On Sat, Nov 12, 2011 at 12:59 PM, Glenn Maynard
<glenn@zewt.org> wrote:
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.