FF 18 problem?

Well a lot of users calling this morning. I tried Tyler___Durdens patch hopefully it works.

Quote:

---

Originally Posted by Tyler___Durden

You can also implement it like this

Code:

---

Ext.onReady(function(){

  if (Ext.firefoxVersion >= 18) {
      var noArgs = [];
      Ext.override(Ext.Base, {
      callParent : function(args) {
        var method, superMethod = (method = this.callParent.caller) && (method.$previous || ((method = method.$owner ?
method :
method.caller) && method.$owner.superclass[method.$name]));

        // Workarround for Firefox 18. I don't know why this works, but it does. Perhaps functions wich have
        // a try-catch block are handled differently
        try {
        } catch (e) {
        }

        return superMethod.apply(this, args || noArgs);
      }
    });
  }
});

---

This way you don't need to change the ExtJs Files...

---

Thanks, actually I tried this first but it wasn't working for me and caused another error somewhere...will check this..really annoying bug with FF18 and just 2 days before our release :(

Better than after, so you can be sure that it wasn't your fault ;) Just a little explanation to my post, i've want to say that you can put the code anywhere in your ExtJS Application, i prefer it at the startup. Because it is an override to Ext.Base:callParent you don't have patch the library files, i've placed it right after Ext.onReady...

I applied the patch directly at the start in some function in Ext.onReady. Three users notified that their problem was gone. Following Mozilla's bugthread it should be gone because the function isn't compiled anymore with a try catch in it.

Someway it is an amazing bugfix Tracking the problem down to the new JIT engine and bypass the compilation of the code with a try catch. =D> Lets call it a Hack...=P~

Quote:

---

Originally Posted by evant

Not really useful to speculate without seeing a test case, please post one.

---

Here's the test case:

Quote:

---

Originally Posted by dwoosley

Here's the test case:

---

1. Code was working fine in FF, no changes to the code.
2. FF was upgraded, Ext is now broken.

After implementing the workaround I am immediately met with a "Too much recursion" error.

We're using ExtJS 4.1.0

Thoughts? anyone?

Thanks,
Luke

Holger and Tyler Thanks! Your patch fixed our company's application too. The most used page of our critical internal application was not displaying information correctly without the work around. Thanks again for posting this information.

I also get the error "Too much recursion" after using the workaround.

c2c-guinness did you manage to get it to work?

Thanks

Is Sencha going to package this into a hot fix release or main stream release soon?

For some reason actually applying this using Override is causing errors while patching the libraries directly for me worked fine.