+1 on this bug causing problems for my company. This has become a serious issue for us trying to migrate our flagship app (which is an intranet based app that we deploy on customer intranet servers) to more up-to-date standards. We've tested the 4.0.7 code base, but the fix for the issue isn't present in that stream of code. Any word on which version of ExtJs will contain the fix?
Give a small update on this. At SenchaCon I showed the guys it was still broken at least for isiE7 in 4.0.7.
I took a look and Ext JS 4.1 beta 1 has this finally fixed.
Ext JS 4.1 pr1 had the same as 4.0.7 when Don and I looked at it on his laptop after one of the sessions.
Ext JS 3+ hasn't had any updates yet and probably won't have any public release.