24 Dec 2012 2:39 PM #1
Unanswered: Picker Field Issues with Chrome Version 17+
I'm a bit confused. I've spent countless hours with this, and haven't found a solution for it yet. I've come across a few various bug reports in the forums, but they've been closed with no action response, and other various posts have stated that it doesn't affect them, so I'm not sure what the current status is on the problem.
Anywho, the problem is that it appears with all different pickers, including the datepickerfield, if you're using a relatively recent version of Chrome, you are unable to select the last element in the picker. That is, if you select December, 31, or 2012, it immediately pops up to the element just prior to that point (ex. November, 30, or 2011). I've tried this with Sencha Touch 220.127.116.11, and Sencha Touch 2.1.0. Both still have the same issue.
Are there any available overrides or anything that I can use to resolve this problem? Apparently it only began affecting Chrome after version 16 or so, and has persisted all the way until the current version (currently version 23). It doesn't affect Safari, or iOS or Android. However, my user base, as well as my testing platform, is heavily Chrome dependent, and has made using the field difficult, if not impossible.
Any help or ideas to fix (or at least band-aid) the problem, would be much appreciated. Thanks!
26 Dec 2012 7:36 AM #2
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
It was marked closed because it's a chrome only issue but I'm going to ping the core dev to see if we can at least open it and look at it again.Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
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 email@example.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.
26 Dec 2012 5:48 PM #3
3 Jan 2013 2:12 PM #4
Looking forward for any possible solutions!
Thanks in advance!
28 Oct 2013 5:50 AM #5mitchellsimoensIt was marked closed because it's a chrome only issue
what does this mean?
chrome is not supported by sencha touch? u dont care if it not works in chrome?
we dont want a native app, its part of our concept to run the app in browser!
i was updating from 2.0 to 2.3 just because this bug. (our app is in use and our people need the datepicker feature extensivly).
i really thought this will help, but its still the same issue.
workaround fixes will not help, because i use the build-function from architect.
what can we do?