-
26 Dec 2012 12:58 PM #1
Ext.fx.layout.Card ChromeMobile
Ext.fx.layout.Card ChromeMobile
Hi,
i was wondering, why is Ext.fx.layout.Card forced to type = "scroll" on ChromeMobile?
I removed the following condition in Ext.fx.layout.Card`s Constructor (ST 2.1)
and there seems to be no issue with ChromeMobile on my Samsung Galaxy S2 (Android 4.0.4, latest Chrome from Google Play).Code:else if (type === 'slide' && Ext.browser.is.ChromeMobile) { type = 'scroll'; }
It would be nice to use animations on Chrome, especially for the NavigationView which uses Card Layout and Card FX by default.
Thanks
-
28 Dec 2012 7:27 AM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 34,117
- Vote Rating
- 453
Chrome has had bugs so to support every version of Chrome the anims may have to be disabled. Also, I wouldn't edit a ST class, would make it hard to upgrade to a newer ST version, instead override the method.
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.
-
28 Dec 2012 9:26 AM #3
Thank you for your reply Mitchel.
I will put my changes in a separate override Class if i use it for production of course.
But can you tell which Versions of ChromeMobile had this bugs you mentioned?
So i could disable the animations only until a specific Version as there are definitly no problems with the current iOS and Android Versions anymore.
Thanks in advance!


Reply With Quote