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!

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.

Avatar for Username

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

Denc nañu waxtaan wii. Yónneel yeneen laaj soo soxlaa ndimbal.

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 tontu
  • 2 am na jafe-jafe bii
  • 1 view
  • i mujjee tontu mooy rwmitchell

rwmitchell
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.

Saafara biñ tànn

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.

Jàng tontu lii ci fi mu bokk 👍 0

All Replies (1)

rwmitchell
rwmitchell Ki laajte
more options

Saafara yiñ Tànn

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.