Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#14633 closed enhancement (fixed)

Reconsider Android input field jumping workaround

Reported by: Atsushi Ono Owned by: ykami
Priority: high Milestone: 1.8
Component: DojoX Mobile Version: 1.7.1
Keywords: Cc:
Blocked By: Blocking:

Description

There was the Android input field jumping issue in ScrollableView (reported as a part of #12732) caused by Android webkit bug. Dojo 1.7/1.7.1 has some workaround code to avoid it, but it's a quite tricky code and hard to maintain. We need to reconsider it to find the better way to avoid the issue.

Attachments (2)

14633.patch (8.9 KB) - added by Atsushi Ono 8 years ago.
[patch][ccla] patch to use top/left style for scrolling animation
14633-2.patch (851 bytes) - added by Atsushi Ono 8 years ago.
[patch][ccla] update for Android > 3

Download all attachments as: .zip

Change History (9)

comment:1 Changed 8 years ago by ykami

Milestone: tbd1.8
Status: newassigned

comment:2 Changed 8 years ago by ykami

In [27589]:

Refs #14633 !strict. Removed the android input field jump issue workaround code as the first step.

comment:3 Changed 8 years ago by ykami

In [27592]:

Refs #14633 !strict. Removed the android input field jump issue workaround code as the first step.

Changed 8 years ago by Atsushi Ono

Attachment: 14633.patch added

[patch][ccla] patch to use top/left style for scrolling animation

comment:4 Changed 8 years ago by Atsushi Ono

I have attached a patch to avoid input field jumping issue in scrollable widgets. In case of Android, using "-webkit-transform:translate3d(x,y,z)" style causes this issue, so in this patch "top"/"left" styles are used instead for scrolling animation, which can prevent this issue.

comment:5 Changed 8 years ago by ykami

Resolution: fixed
Status: assignedclosed

In [28121]:

Fixes #14633 !strict. A fix for the input field jump issue on Android devices. Applied onoat's patch. Thanks onoat for the patch.

Changed 8 years ago by Atsushi Ono

Attachment: 14633-2.patch added

[patch][ccla] update for Android > 3

comment:6 Changed 8 years ago by Atsushi Ono

In case of Android 3.0 or later, the previous scrolling using -webkit-transform:translate3d(x,y,z) is much smoother than using top/left, so we should use top/left by default only for Android 2.x. I have attached a patch for this update.

comment:7 Changed 8 years ago by ykami

In [28139]:

Refs #14633 !strict. Do not apply the top/left workaround to android 3.0 or later.

Note: See TracTickets for help on using tickets.