Hybrid View
-
22 Apr 2012 1:09 PM #1
Touchmove, Touchstart, Touchend targets wrong in iOS
Touchmove, Touchstart, Touchend targets wrong in iOS
REQUIRED INFORMATION
Ext version tested:- Touch 2.0.0GPL and 2.0.1RC
- iOS 5.1
- HTML5
- When I have a touchmove event and I track the target, it works in Chrome but in iOS the touch target is ALWAYS the first thing I touched. Even if I drag my finger to a different element, the same element.id comes back again and again.
- Check out http://roycyang.github.com/sencha-touch-extensions/ in the debug console
- Note how in Chrome or Safari if you click on the GT.FixedButton, the target changes when you move your cursor?
- Doing the same thing in iOS gives you the wrong target
- That the target element is actually what you are touching
- The target never changes, is always the first thing you touched
Code:https://github.com/roycyang/sencha-touch-extensions
HELPFUL INFORMATION
Screenshot or Video:- attached
Screen Shot 2012-04-22 at 4.57.14 PM.jpg
The touchmove target never changes in iOS:
photo.jpg
See this URL for live test case: http://roycyang.github.com/sencha-touch-extensions/
-
23 Apr 2012 7:27 AM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 34,120
- Vote Rating
- 453
Thanks for the report.
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.
-
30 May 2012 11:52 PM #3
any fix?!?
any fix?!?
did you found any fix for this issue?!
-
23 Jul 2012 12:01 PM #4
Fix
Fix
I need this fix too. Are there any solution?
-
29 Nov 2012 12:24 AM #5
It's not fixed on ST2.1 (Build date: 2012-11-05 22:31:29)
The temporary solution:
Code:onElementTouchMove: function(e) { if (Ext.browser.is.ChromeMobile) { var x = e.event.changedTouches[0].screenX; var y = e.event.changedTouches[0].screenY; } else { var x = e.pageX; var y = e.pageY } var target = document.elementFromPoint(x, y); }
Success! Looks like we've fixed this one. According to our records the fix was applied for
TOUCH-2809
in
2.1.


Reply With Quote