On Thu, Apr 14, 2011 at 09:01, Kenneth Russell <k...@google.com> wrote: > Adding support for asynchronous initialization of WebGL is a good > idea, and should be proposed on public_webgl, but this discussion > should focus solely on improving the specification of the existing > synchronous initialization path, and its error conditions.
I don't think the added complexity/verbosity provides any advantage over my proposal above (for the applications that even desire to show additional failure information). Is there a scenario I overlooked? Regards,