On Mar 11, 2011, at 1:32 PM, Gregg Tavares (wrk) wrote:
>
>
> On Fri, Mar 11, 2011 at 9:07 AM, <
steve@sjbaker.org> wrote:
>
> > It would be nice if the browsers could optionally provide more detail
> > about the reason the context wasn't available.
> >
> > In my case if my app could get the information that I had an acceptable
> > video card but the driver version was too old and I'd need to update it --
> > I'd build that in to my app to provide better info for a user about how to
> > get a working version.
>
> I too would like that. One way I try to deal with that is to redirect the
> user to
http://get.webgl.org - which at least provides a central point for
> detecting, diagnosing and explaining to the end user why he's not getting
> any pretty graphics...and perhaps offering advice about what to do about
> that. That web site has gotten a lot better recently - and it's always
> the first place I go when I have a machine that won't produce a webgl
> context.
>
>
> If they don't have webgl you should direct them to
http://get.webgl.org
>
> if (!window.WebGLRenderingContext) {
> // the browser does not know what webgl is
> // present a link or redirect to
http://get.webgl.org
> }
>
> If they DO have webgl but it won't initalize you should direct them to
http://get.webgl.org/troubleshooting
>
> gl = canvas.getContext("webgl");
> if (!gl) {
> // present a link or redirect to
http://get.webgl.org/troubleshooting
> }
>
>
>
> There is no good reason for every application to have to handle this
> individually.