Reproducible with: Firefox 31 Release - 20140716183446 - User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 Firefox 32 Beta 1 - 20140722195627 - User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0 Environment: Windows 7 + NVidia NVS 5100M Steps to reproduce: 1. Firefox 30 is installed at some location. 2. Create "spoofed-firefox.bat" file with following content (pointing to location of Firefox 30): SET MOZ_GFX_SPOOF_WINDOWS_VERSION=60001 SET MOZ_GFX_SPOOF_VENDOR_ID=0x10de SET MOZ_GFX_SPOOF_DEVICE_ID=0x0a6c SET MOZ_GFX_SPOOF_DRIVER_VERSION=8.17.12.58 "C:\Mozilla\Firefox\firefox.exe" -p -no-remote 3. Open "spoofed-firefox.bat" to launch Firefox 30, create a new profile, start Firefox 30, and verify "about:support" ----> Graphics > Direct2D Enabled = true - OK 4. Close Firefox 30, then update it to Firefox 31 or 32. 5. Open "spoofed-firefox.bat" to launch Firefox (now updated to 31/32), select the SAME profile as at step #3, start Firefox, and verify "about:support" ----> Graphics > Direct2D Enabled Expected results: Direct2D is Blocked. Actual results: Direct2D is still Enabled. Notes: - if after step #3 the user creates a new profile, then Direct2D will be Blocked as expected - this issue is a follow-up for fix in bug 988549 - the impact on the user is: for a user that has a driver version NOT blocked in Firefox 30, but blocked in Firefox 31/32, updating Firefox will NOT block Direct2D as expected, and so it may cause problems ***** Both Firefox 33 Aurora and 34 Nightly (latest) seem to not have this issue (different patch was applied in Aurora, so the changes for non-Intel card drivers that are affected by this bug were not added there - see https://bugzilla.mozilla.org/show_bug.cgi?id=988549#c67 and https://bugzilla.mozilla.org/show_bug.cgi?id=988549#c69)