Changes between Version 2 and Version 3 of Ticket #17502, comment 6


Ignore:
Timestamp:
Oct 14, 2013, 5:13:36 PM (8 years ago)
Author:
Adrian Vasiliu
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #17502, comment 6

    v2 v3  
    44The cause of this issue is simple: dojox/mobile/scrollable calls e.preventDefault() on dojo/touch#press *except* if the target is an input field. Hence, when starting the scrolling over the input field, the browser scroll is not prevented. Now, the reason why we don't preventDefault for input fields is that doing so would forbid the keyboard from showing up.
    55
    6 I have tested the following quick solution: instead of doing a selective preventDefault() on touch.press, doing it always (including for input fields) on dojo/touch#move. This improves the situation on both iOS and Android. However, scrolling very slowly starting from an input field pops the keyboard. Globally I think this is still preferable than the current behavior, but I try to find a solution for this last glitch too - it seems due to the synthetic clicks generated by dojo/touch.
     6I have tested the following quick solution: instead of doing a selective preventDefault() on touch.press, doing it always (including for input fields) on dojo/touch#move. This improves the situation on both iOS and Android. However, scrolling very slowly starting from an input field pops the keyboard. Globally I think this is still preferable to the current behavior, but I try to find a solution for this last glitch too - it seems due to the synthetic clicks generated by dojo/touch.