Re: [Public WebGL] Odd behavior on eePC netbook.

[Steve Baker <steve@sjbaker.org>]

Vladimir Vukicevic wrote:
> ----- Original Message -----
>   
>> So what about Firefox? Is it punting on context creation because the
>> maximum fragment shader length that the hardware can support is less
>> than some minimum spec or something? Should Chrome (technically) be
>> punting too?
>>     
>
> Nope -- Chrome is using ANGLE by default, so is going through dx9.  We're only trying to create a GL context, which being GL 1.4, won't have sufficient capabilities for WebGL.  You can get a somewhat out-of-date test extension from http://people.mozilla.com/~vladimir/misc/angleproject.xpi that'll enable ANGLE in Firefox, though we're working on getting it available in the core build.
>
>     - Vlad
>   
Ah!  That makes perfect sense.  Thanks!

Now - why no error messages after a failed shader link in Chrome?   Is
it just that the underlying driver isn't being too communicative - or is
ANGLE failing to get the right error returns from DX9?

  -- Steve

-----------------------------------------------------------
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: