Ce site disposera de fonctionnalités limitées pendant que nous effectuons des opérations de maintenance en vue de vous proposer un meilleur service. Si un article ne règle pas votre problème et que vous souhaitez poser une question, notre communauté d’assistance est prête à vous répondre via @FirefoxSupport sur Twitter, et /r/firefox sur Reddit.

Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

Firefox 22.0 serious closure bug

  • 4 réponses
  • 2 ont ce problème
  • 2 vues
  • Dernière réponse par 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?

Modifié le par mccodev

Solution choisie

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

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (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 Auteur de la question
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??

Modifié le par mccodev

mccodev
mccodev Auteur de la question
more options

Solution choisie

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