-
22 Aug 2011 1:00 PM #11Sencha - Community Support Team
- Join Date
- Jan 2009
- Location
- Palo Alto, California
- Posts
- 1,941
- Vote Rating
- 6
Ok, I've sent one of our guys to check this out. If we roll a 4.0.7 it will likely make it into that
Ext JS Senior Software Architect
Personal Blog: http://edspencer.net
Twitter: http://twitter.com/edspencer
Github: http://github.com/edspencer
-
22 Aug 2011 1:03 PM #12
Is 4.0.6 coming out this week?
I still have a few issues with Menu that wasn't addressed in 4.0.5.
Thanks Ed.
Ron
-
24 Aug 2011 1:48 PM #13Sencha - Community Support Team
- Join Date
- Jan 2009
- Location
- Palo Alto, California
- Posts
- 1,941
- Vote Rating
- 6
Ext JS Senior Software Architect
Personal Blog: http://edspencer.net
Twitter: http://twitter.com/edspencer
Github: http://github.com/edspencer
-
25 Oct 2011 7:48 AM #14
+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?
-
25 Oct 2011 8:49 AM #15
I'm at SenchaCon and will ask the guys what the status is on this bug and try to find more information about it.
-
7 Feb 2012 12:44 PM #16
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.
This duplicates another bug already reported in our system:
EXTJSIV-3467


Reply With Quote