We should stop doing an explicit search for Java plugins in Firefox 4. We would like to treat all NPAPI plugins equally, removing Java as a special case is an important step. The Firefox 4 target allows Java plugin vendors to update their installers. (Side note: we should also remove special UI for disabling Java and have users simply use the addons manager to disable/enable Java plugins).
Java plugin vendors should follow the registry-based solution outlined here: https://developer.mozilla.org/en/Plugins/The_First_Install_Problem
Changing summary to reflect a Gecko 1.9.3 target, need Sun to tell us what the first version of Java that will not require us to check Java-specific registry keys is.
Sun (became Oracle) has implemented the registry-based solution which is currently scheduled to be in JRE 6 update 21 release. We'd like to get a Firefox version which implements the registry based solution for testing our fix.
Created attachment 441529 [details] [diff] [review] fix v1.1
We probably shouldn't do this in Gecko 1.9.3. Lets do it in whatever comes after Gecko 1.9.3.
Is this still wanted? The patch has been rotted by http://hg.mozilla.org/mozilla-central/rev/8b86086e5f0e ; would it help if I updated it?
We want this patch, but not yet. Maybe in six months.