FF 18 problem?

[panpur]

Hello,

I recently updated Firefox & apparently it breaks my application partially. It works fine on Chrome & previous version of FF.
Firebug is disabled.
Also the problem seems to occurs on fairly complex window. I have a window with border layout, tree on left, chart on top, & grids on the center inside card layout.
Other simpler windows seems to works fine.
Another weird thing is, if Firebug is enabled, then then problem seems to go away.

Does anyone having similar problem on FF 18?
ExtJS version used: ext-4.1.1

[panpur]

So it seems the problem lies on Card Layout.
I have 8 grids inside it.
If I only have 5 grids then the window displayed correctly.
So I guess the workaround is to have 5 grids initially & dynamically add other grids later when clicking tree node.

[zloi]

Also have problem with FF18. In console i have
TypeError: d.caller is null ext-all.js:21
TypeError: g is undefined ext-all.js:21

[evant]

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

[pzs1]

I have same problem with FF18 and ExtJS 4.1.1:

TypeError: callOverrideParent.caller is null
.../extjs/ext-all-dev.js Line: 37

Interestingly if Firebug console is open the error does not come up.

If I find the cause of the problem, i will post here.

[Tyler___Durden]

Same Problem here, seems to be avoidable by disabling javascript.options.ion.content in about:config. Is this maybe a problem with the new Ionmonkey JIT Compiler?

Cheers

[zloi]

Same Problem here, seems to be avoidable by disabling javascript.options.ion.content in about:config. Is this maybe a problem with the new Ionmonkey JIT Compiler?

Cheers

disabling IonMonkey solved the problem

[evant]

A test case would be quite useful, I was running through our examples and a few other trivial test cases and wasn't able to reproduce it. IonMonkey was on.

[Tyler___Durden]

A test case would be quite useful, I was running through our examples and a few other trivial test cases and wasn't able to reproduce it. IonMonkey was on.

we currently try to produce a running or better said failing example. I also haven't found one in the ExtJS examples. For me it seems to happen if a child component is added to a component after the parent component was already rendered. Something like this...

[pzs1]

For me it seems to happen if a child component is added to a component after the parent component was already rendered. Something like this...

So far I have got something similar... but the problem haven't