[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] (summarizing) Canvas.getContext error handling


On Fri, Apr 29, 2011 at 20:08, Benoit Jacob <bjacob@mozilla.com> wrote:
> ** Exceptions are a single unified mechanism; while with the
> webglcontextcreationerror way, every new canvas context type will have to
> introduce its own event type.

This argument implies the Canvas spec defines an exception object that
works for every potential new canvas context type.
Otherwise, every new canvas context type would still have to define
the exception object it throws.

> So, no clear advantage for either option.

One advantage of an event over an exception is that it does not
interfere with debugging tools (eg. "break on error") - just to pass
to the application mere "additional information" that it might not
even want/need and should be used for debugging purposes only [1].

[1] Because there is no standardized statusMessage strings that an
application could use for something useful besides displaying it.
Anyways, a browser can present more useful and consistent
troubleshooting UI than every application ever could... imho the
troubleshooting/reporting problem should not be pushed to application

You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl