All users were logged out of Bugzilla on October 13th, 2018
When I go to the plugin check website, I am immediately redirected to: http://java.com/en/download/ In the same tab as the plugin check so I can never read the content on the plugin check website. It should open the website in another tab or window.
Summary: Unable to use the plugin check site → Unable to use the plugin check site (redirect to java)
works for me, schalk any idea what can cause this problem ?
Assignee: nobody → cbook
I understand what the bug is I went to the plugin page and it told me that my Java was out of date and presented a dialog with three choices (Update and two others). I clicked Update but then decided not to update right then. Once you've done that, now every time you go to the plugin check page, it navigates to the Java page without any confirmation. It should show the confirmation dialog again.
Hey All, I also just tested this an cannot reproduce this at all. Michael, which URL are you using to access plugincheck? I for example also do not see the dialog with the three choices you refer to at all. Can you please attach a screen shot of this? Thanks!
Created attachment 743229 [details] Screenshot Here's the dialog along with the plugin check page. I go to about:addons and then click on "check to see if my plugins are up to date" When I click on "Update", Firefox is navigated to java.com/en/download. So it appears the Firefox is invoking some Java for the plugin check, and once you've clicked update, subsequent opens of the page navigate directly to the java page. Maybe this is a Sun bug?
Oracle bug :)
(In reply to Michael Kaply (mkaply) from comment #4) > Created attachment 743229 [details] > Screenshot > > Here's the dialog along with the plugin check page. > > I go to about:addons and then click on "check to see if my plugins are up to > date" > Oooooh, so that dialog is not related to the plugincheck page but is triggered by the browser. I reckon that is happening is that the part of plugincheck that determines your Java version, runs a little applet in the visually hidden and this triggers the browser's built in update notice for Java. With regards to the continues redirect after you clicked update, this might be the intended behavior (although I doubt it) or, a bug in Firefox. Either way we need to redirect this bug so it gets in front of the right audience, unless I am completely of the tracks that is. Carsten you agree?
(In reply to Schalk Neethling [:espressive] from comment #6) > With regards to the continues redirect after you clicked update, this might > be the intended behavior (although I doubt it) or, a bug in Firefox. Either > way we need to redirect this bug so it gets in front of the right audience, > unless I am completely of the tracks that is. Carsten you agree? yeah i agree. Also i think thats maybe something where Benjamin or Dolske can help to get the right people here cc'd. Benjamin, Dolske, can you take a look at Schalks Analysis in comment #6 . Is this a Firefox Bug ?
(In reply to Carsten Book [:Tomcat] from comment #7) > (In reply to Schalk Neethling [:espressive] from comment #6) > > With regards to the continues redirect after you clicked update, this might > > be the intended behavior (although I doubt it) or, a bug in Firefox. Either > > way we need to redirect this bug so it gets in front of the right audience, > > unless I am completely of the tracks that is. Carsten you agree? > > yeah i agree. Also i think thats maybe something where Benjamin or Dolske > can help to get the right people here cc'd. > > Benjamin, Dolske, can you take a look at Schalks Analysis in comment #6 . Is > this a Firefox Bug ? urks now actually cc'd
The dialog shown in attachment 743229 [details] isn't a Firefox dialog (nor does Firefox itself do any plugin update checking/installing, other than blocking some versions of some plugins). I'd suspect this is entirely a Java bug/annoyance. Do other pages with a Java applet also autonavigate to the Oracle update page?
You are correct, it's happening with any applet page. It's quite a horrible user interface. IT just replaces the applet page with the Java download page. We should probably talk to them about this and at least try to get them to open it in a new tab or something. It makes the plugin check page completely unusable.
mcoates has contacts. We should at least make sure that our support system is aware of this behavior.
Assignee: cbook → nobody
Component: plugins.mozilla.org → Java (Oracle)
Product: Websites → Plugins
QA Contact: cbook
Yes, I can communicate over whatever we need to let them know. What is the end issue and recommended change we want to tell?
Java should never redirect the user's current page to http://java.com/en/download/
Thanks! I summarized the details and sent that recommendation over. I offered to also work with them to setup a bugzilla account so we can directly copy them into Java related bugs as needed.
I lead the Java sec pgm and work with Michael. I will escalate to attention of relevant staff on the Java team.
The dialog in the screen shot will be shown only when Java Plugin's dll is loaded and we detected the Java Plugin is expired/old. I tried to visit the mozilla plugin check page: http://www.mozilla.org/en-US/plugincheck/ My machine has old Java 7u17 installed - and so the plugincheck page displayed "update now" button. Clicking the "update now" button directs me to: http://www.java.com/en/download/manual.jsp Both of the above page did not trigger loading of any Java related dll into the Firefox process. Both page does not contain any Java applet. How to reproduce the problem exactly ?
To reproduce the problem, have that dialog display. Then click on Update, but choose not to update your Java right then. From then on in that session, any time you open plugin check or go to a page with an applet, you will be navigated away from that page to the java install page, with no dialog. The dialog should appear again. It shouldn't navigate to the java download page.
Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/ If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
Product: Plugins → Plugins Graveyard
You need to log in before you can comment on or make changes to this bug.