Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

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

搜索 | 用户支持

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

详细了解

With Firefox 9.0.1 an app using a javascript confirm command doesn't display the message. Popup blocker is turned off for this app's domain.

  • 1 个回答
  • 2 人有此问题
  • 1 次查看
  • 最后回复者为 rwmitchell

more options

Application is written in php and javascript. Clicking on a button triggers a javascript confirm dialog. Since upgrading to Firefox 9.0.1 the confirm dialog is not displayed. Popup blocker was first set to allow the app's complete domain, then turned off altogether. Javascript is enabled.

Application is written in php and javascript. Clicking on a button triggers a javascript confirm dialog. Since upgrading to Firefox 9.0.1 the confirm dialog is not displayed. Popup blocker was first set to allow the app's complete domain, then turned off altogether. Javascript is enabled.

被采纳的解决方案

Turns out that Firefox became a little more fussy about standards than IE. (Imagine that!!) Code created hidden inputs of type="text" , then called a javascript function and passed the values in the hidden inputs as parameters. The original code just passed the name of the input as a variable. The Firefox Webconsole then complained that the variable was not declared. Once I passed the variable.value, then the error went away, Firefox was happy, didn't break IE, so I'm happy.

定位到答案原位置 👍 0

所有回复 (1)

more options

选择的解决方案

Turns out that Firefox became a little more fussy about standards than IE. (Imagine that!!) Code created hidden inputs of type="text" , then called a javascript function and passed the values in the hidden inputs as parameters. The original code just passed the name of the input as a variable. The Firefox Webconsole then complained that the variable was not declared. Once I passed the variable.value, then the error went away, Firefox was happy, didn't break IE, so I'm happy.