This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Problem with firefox 11 and jre 1.6.0_31

  • 5 balasan
  • 95 ada masalah ini
  • 2 paparan
  • Balasan terakhir oleh lunarwater

more options

Hi, I have a problem with firefox 11 and jre 1.6.0_31, if you open a page (using window.open) and this page contains a signed applet embedded, the object window.opener refers to the self page, but if this page doesn't have an applet, the window.opener refers to the correct page.

This works fine on IExplorer 9 and jre 1.6.0_31 or firefox 10 with jre 1.6.0_29 and with older versions of firefox.

Hi, I have a problem with firefox 11 and jre 1.6.0_31, if you open a page (using window.open) and this page contains a signed applet embedded, the object window.opener refers to the self page, but if this page doesn't have an applet, the window.opener refers to the correct page. This works fine on IExplorer 9 and jre 1.6.0_31 or firefox 10 with jre 1.6.0_29 and with older versions of firefox.

All Replies (5)

more options

Hi, This forum is focused on end user support. You can try looking for documentation on our developer site - https://developer.mozilla.org/ or try asking questions in a place like stack overflow - http://stackoverflow.com/ Sorry for the inconvenience.

more options

I have raised a bug report here: https://bugzilla.mozilla.org/show_bug.cgi?id=747542

Hopefully some Dev will fix this :D

more options

The bug report didn't appear to match the problem, so I tried to create a ticket myself as well. Please please fix

https://bugzilla.mozilla.org/show_bug.cgi?id=754876

more options

The problem occured since FF11. It is still there in version FF13. Is there any known workaround?

more options

The only workaround I can think of currently is to place the applet in a frame -or- iframe, while parent frame maintains the proper reference to window.opener. Then change your calls to use parent.opener