User Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0 Build ID: 20120710123126 Steps to reproduce: I tried to spoof the vendor ID on my Intel 945 graphics card, just to see what would happen. I ran the following two commands: set MOZ_GFX_SPOOF_VENDOR_ID=0 firefox Actual results: The vendor ID was set to 0 in about:support, but this resulted in all acceleration being blocked with the statement "Blocked for your graphics card because of unresolved driver issues." (This is not the case if I do not spoof the VENDOR_ID) Expected results: Everything should have been unblocked, as Vendor ID 0 does not exist, and thus should not have any options blocked.

You wrote "no longer works". Did this ever work ? We have a whitelist for graphic cards on windows and if your vendor ID is unkown then you get blocked. (bug 623338)

It's supposed to work--see Bug 604771 Comment 0.

(In reply to Terrell Kelley from comment #2) > It's supposed to work--see Bug 604771 Comment 0. It was originally supposed to work, but block-unless-known-good is really how we have to do things. This is not to say that we couldn't add an exception for the (I would imagine) clearly-spoofed '0x0000' id. Would this provide functionality not possible with the existing available prefs? (force-enable and such?)

For the record, graphic drivers are not blocklisted for D3D9, D3D10 and D2D on Windows 8 based on their version. See bug 706908.

Yeah, while that was the intention in Bug 604771 Comment 0, clearly bug 623338 changed that and so that must have been this way for a year and a half now. Not interested in changing it... also I don't understand why anyone would care about that. If one wants to circumvent the blacklist, force-enabled prefs are all one needs. (In reply to Jeff Gilbert [:jgilbert] from comment #3) > Would this > provide functionality not possible with the existing available prefs? > (force-enable and such?) Not at all. force-enabled prefs do completely circumvent the blacklist.

(In reply to Benoit Jacob [:bjacob] (mostly away) from comment #5) > Not at all. force-enabled prefs do completely circumvent the blacklist. I see browser console messages: Error: WebGL: Disallowing antialiased backbuffers due to blacklisting. base.js:3131:109 Error: WebGL: Error during ANGLE OpenGL init. base.js:3131:109 I have set 7 different prefs with suffix "force-enabled" to true why does it still say blacklisted?

Clarifying my previous comment: I have a driver older than the minimum driver version numbers (as described in Bug 623338) and have set 7 different prefs with suffix "force-enabled" to true would you expect to get "blacklisting" message mentioned. I am testing this case before trying the VENDOR_ID = 0 test.