Closed Bug 736232 Opened 12 years ago Closed 10 years ago

remove window.WebGLRenderingContext object if GPU is blacklisted

Categories

(Core :: Graphics: CanvasWebGL, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: paulirish, Unassigned)

Details

(Whiteboard: webgl-next)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/536.3 (KHTML, like Gecko) Chrome/19.0.1070.0 Safari/536.3

Steps to reproduce:

* Open Firefox on a machine with a blacklisted GPU.
* See if `WebGLRenderingContext` is falsy, as we already know (synchronously) that the GPU can't support WebGL content



Actual results:

It is truthy. Now my feature detection breaks and I'm going to try to give my users a webgl experience instead of telling them to upgrade their GPU.


Expected results:

WebGLRenderingContext should have been falsy and I could have routed my user to non-webgl content.
Whiteboard: webgl-next
Component: Untriaged → Canvas: WebGL
Product: Firefox → Core
We won't always know if we're going to blocklist a driver until we create a context for it. Since we can't tell 100% of the time, is it worth giving this hint where we can? I don't see how it'd be useful, given that its presence isn't authoritative.

You should fix your feature detection to handle context creation failure, regardless.
Status: UNCONFIRMED → NEW
Ever confirmed: true
I'm going to mark this WONTFIX, since it's not really ever usefully authoritative. That is, no one should ever rely on the behavior here, and trying to do a partial implementation might just encourage people to assume that this should work.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.