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

This thread was archived. Please ask a new question if you need help.

Firefox 22.0 serious closure bug

  • 4 replies
  • 2 have this problem
  • 1 view
  • Last reply by cor-el

mccodev
mccodev
more options

We have run into what seems like a serious closure bug in Firefox 22.0.

The simple following code executes fine in IE and chrome etc. but fails in a very scary way in FireFox - it thinks the function is undefined !!!

if (true) { 

   test();

   function test()  {
       alert("success")
   }

}

If the code is executed outside of the if statement (or if just the function definition is moved outside the if statement) everything is ok.

The same error occurs (not defined) inside other closures like do .. while etc.

We are scared. What did we miss?

We have run into what seems like a serious closure bug in Firefox 22.0. The simple following code executes fine in IE and chrome etc. but fails in a very scary way in FireFox - it thinks the function is undefined !!! if (true) { test(); function test() { alert("success") } } If the code is executed outside of the if statement (or if just the function definition is moved outside the if statement) everything is ok. The same error occurs (not defined) inside other closures like do .. while etc. We are scared. What did we miss?

Modified by mccodev

Chosen solution

This has been solved. Firefox is different from other browsers (as we know)... but here's why...

http://stackoverflow.com/questions/18079086/firefox-22-0-scope-bug

Read this answer in context 👍 0

All Replies (4)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Just swap the order of the two statements and place the function definition before calling the function. 

if (true) {
   function test()  {
       alert("success")
   }
 test();
}
mccodev
mccodev Question owner
more options

Thank you for your time and advice... but that wasn't my point at all.

The point is this seems to be quite a big bug. Javascript by it's very nature can forward reference within scope. As I suggested, the code works fine in all other browsers.

I'm worried this is a huge new bug in Firefox - or worse a secret breaking change. Has anyone got a lead on this? This should work right ???? Is it just me??

Modified by mccodev

mccodev
mccodev Question owner
more options

Chosen Solution

This has been solved. Firefox is different from other browsers (as we know)... but here's why...

http://stackoverflow.com/questions/18079086/firefox-22-0-scope-bug

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

I've marked your previous post as the solution since you wrote that it has been solved (Firefox doesn't allow forward reference if a function is defined within a block).