Closed
Bug 583566
Opened 15 years ago
Closed 12 years ago
Remove support for plugin.scan.SunJRE
Categories
(Core Graveyard :: Plug-ins, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla21
People
(Reporter: edggar, Assigned: Cykesiopka)
References
Details
(Keywords: helpwanted, Whiteboard: [mentor=bsmedberg][lang=c++][os=windows])
Attachments
(1 file, 1 obsolete file)
7.19 KB,
patch
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8
Updating from 1.6.0.20 to 1.6.0.21 the Java plugin now shows up under plugins despite having plugin.scan.SunJRE set to "99.0".
Reproducible: Always
Steps to Reproduce:
1.Set plugin.scan.SunJRE to a high value like 99.0
2.Install Java 1.6.0.21
3.
Actual Results:
The Java plugin is being listed.
Expected Results:
Java plugin should not be listed under plugins.
I am seeing the same thing with Thunderbird/3.1.1 Gecko/20100713 but it should affect all builds of Firefox and Thunderbird using said Java version.
Comment 1•15 years ago
|
||
Oracle changed the vendor strings with 1.6.0.0.21 from Sun to Oracle
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6969236
Fixed for me with rv:1.9.2.9 Gecko/20100824 Firefox/3.6.9.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
And the problem is back with the latest Java 1.6.0.22
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 5•13 years ago
|
||
Should setting plugin.scan.SunJRE to "99.0" through about:config then restarting be enough to reproduce?
If so, I can reproduce with a SeaMonkey 2.10a1(pre) build.
Version: unspecified → 1.9.2 Branch
Comment 6•12 years ago
|
||
We should remove support for this preference. All the current+secure versions of Java put their registry keys correctly into HKLM/Software/MozillaPlugins.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: helpwanted
Priority: -- → P3
Summary: plugin.scan.SunJRE ineffective with Java 1.6.0.21 → Remove support for plugin.scan.SunJRE
Whiteboard: [mentor=bsmedberg][lang=c++][os=windows]
![]() |
Assignee | |
Comment 7•12 years ago
|
||
Hi, I was familiarising myself with Mercurial and patches, and I thought I would try and fix this bug...
Sorry if the patch doesn't so the correct thing...
Comment 8•12 years ago
|
||
Comment on attachment 714757 [details] [diff] [review]
Remove plugin.scan.SunJRE pref and associated code
This look perfect. Normally you'd set the "review" "?" "revieweremail" flag, but since I'm the correct reviewer I'll just mark it. I don't think a try run will test anything useful since we don't have tests for out-of-data Java.
Can you upload a final patch for checkin that includes a slightly better commit message (one mentioning Java at least) and includes "r=bsmedberg". After you've done that, add the 'checkin-needed' keyword to the bug.
Attachment #714757 -
Flags: review+
Updated•12 years ago
|
Assignee: nobody → cykesiopka
![]() |
Assignee | |
Comment 9•12 years ago
|
||
Updated patch with better commit message
Attachment #714757 -
Attachment is obsolete: true
![]() |
Assignee | |
Updated•12 years ago
|
Keywords: checkin-needed
![]() |
Assignee | |
Updated•12 years ago
|
Attachment #714860 -
Flags: review?(benjamin)
Comment 10•12 years ago
|
||
Comment on attachment 714860 [details] [diff] [review]
Remove old Java plugin scanning pref and related code
You don't need to request another review on this.
Attachment #714860 -
Flags: review?(benjamin)
Comment 11•12 years ago
|
||
Keywords: checkin-needed
![]() |
Assignee | |
Comment 12•12 years ago
|
||
Ok, sorry about that...
Comment 13•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago → 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla21
Comment 14•12 years ago
|
||
(In reply to cykesiopka from comment #12)
> Ok, sorry about that...
No need to apologise - just something to know for the future.
Thanks for the patch.
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•