User Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0 Build ID: 20120710123126 Steps to reproduce: 1. Open about:config in Firefox 2. Set dom.ipc.plugins.enabled to false. 3. Restart Firefox. 4. Go to a plugin-using website, like YouTube. 5. Open page that uses a plugin. (On YouTube, make sure HTML5 mode is off.) Actual results: plugin-container.exe still loads, and is visible in the task manager (under Plugin Container for Firefox). Expected results: plugin-container.exe should not be running EXTRA INFORMATION: Using Windows 7 or Vista compatibility doesn't fix this, although it works fine on real Windows 7. Windows XP compatibility fixes it, but it also disables aero and, more importantly, forces Firefox to start as an administrator (due to a bad decision by Microsoft), which is a security risk. WHY THIS FEATURE IS NECESSARY: Plugin-container.exe's use adds a fairly large amount of processor overhead on low-end devices. Microsoft is pushing Windows 8 to work on netbooks, which are often are processor bound. Disabling plugin-container.exe often speeds up Flash on these platforms. Video sites other than YouTube (which is quite lean) become very glitchy.
Wait. I didn't have the latest beta on Windows 7. It now also fails there, too. And it again works properly if run in Windows XP SP3 compatibility mode. No other compatibility option helps. (I didn't try earlier Windows modes, though.) Nor does spoofing the OS version (using the graphics blacklist override environment variables) I will gladly do regression testing if someone will tell me how to get previous beta versions. I'm sorry, but I haven't been saving my previous betas like I used to.
dom.ipc.plugins.enabled to false is no longer supported for flash.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Depends on: 769721
Resolution: --- → WONTFIX
Why in the world did you give me this message, making me gear up for having to fight for the right to have the choice of in-process plugins, rather than just tell me "We changed the name of the preference"? And why in the world would you intentionally introduce dissimilarity in how Firefox settings work on Windows XP and later versions? And, finally, why was such a change made in between betas, without even so much as an announcement on the 14.0 features page?
The answers to comment 3 are in bug 769721 comment 0.
You need to log in before you can comment on or make changes to this bug.