I'm meeting with the team tomorrow to get an ETA on 4.0.2. Sorry it's taking us so long to fix this.
I appreciate the communication, Abe... I just hope it's soon, because we spent twice as long converting to 4.0 as we budgeted, and we could easily slip a customer delivery date over this if not fixed soon.
Abe, please fix this! I stopped migrating until there are some bugfixes. We have build five applications with each having up to 25 screens, built in ExtJs 3.01. It has cost us a week to get 3 screens working in ExtJs 4.
Blocking are: the beforeselectevents, this performance issue mentioned here in this thread .... KeyMap events.
We have probably no choise to update to 4.0 because probably next year the support for 3.0 will end. New browsers in the future must be supported, that's the reason we want to go to ExtJs 4.
I hope Sencha is aware of the fact that it has existing customers with complex applications with up to 100 screens. Please Sencha, take care of some better backward compatibility.
Just in case you haven’t seen this thread. It details the browser wide issues and performance comparisons between EXTJS versions. It should give you a good idea as to the scope of the issues we are seeing.
I'll keep you posted as I wrestle this to the ground.
FWIW, I've found in my testing that setting a layout to something other than the default (auto) helps.
I added "layout : 'fit' " in every nested panel of the first example code in this thread and it doesn't change anything sorry. it take between 3 to 5 seconds to show / hide the controls (under Win XP / FF4.0)