Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Problem with firefox 11 and jre 1.6.0_31

  • 5 个回答
  • 95 人有此问题
  • 3 次查看
  • 最后回复者为 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.

所有回复 (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