-
19 Jun 2012 8:01 AM #31
Sencha is dead. WTG guys. Can I get a refund?
Wes
-
20 Jun 2012 7:48 AM #32Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,714
- Vote Rating
- 438
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
________________
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
https://github.com/mitchellsimoens
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services services@sencha.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!
When posting code, please use BBCode's CODE tags.
-
27 Jun 2012 5:38 AM #33
?
?
How to fix that ?
Same problem here (commercial version)
-
27 Jun 2012 5:46 AM #34
Get latest version of Chrome and download latest nightly build.How to fix that ?
Scott.
-
27 Jun 2012 5:56 AM #35
-
3 Jul 2012 9:28 AM #36
Last post: Chrome 20 is out, this is still unfixed.

Wes
-
3 Jul 2012 9:37 AM #37
Please note that 3.4.1 has not yet been released to support subscribers.Last post: Chrome 20 is out, this is still unfixed.
Scott.Last edited by mitchellsimoens; 3 Jul 2012 at 11:45 AM. Reason: Wrong version of Ext .. my mistake
-
5 Jul 2012 6:44 AM #38
Just override with the script in comment #14. it will work over google 18.
-
16 Jul 2012 7:52 AM #39
Some of us have systems with normal,locking,buffering,grouping,locking+buffering,buffering+grouping columns/views and perhaps a few extensions on each of those. Overriding all my code took forever, and now I have to wait until Chrome changes and possibly go back and remove/edit all that code again. This is the opposite of browser independence, we have to spend all our money dealing with one browser issue.Just override with the script in comment #14. it will work over google 18.
Wes
-
20 Aug 2012 6:30 AM #40
What is the status of this? As there been a fix released, I'm now on Chrome 21 and the fix suggested in this thread does not seem to work.
You found a bug! We've classified it as
EXTJSIII-47
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.


Reply With Quote
