Opened 5 years ago

Last modified 2 years ago

#18593 new defect

iOS Selection on short forms causes cursor to jump to end of line

Reported by: szerfas Owned by: Patrick Ruzand
Priority: low Milestone: 1.14
Component: DojoX Mobile Version: 1.10.4
Keywords: Cc:
Blocked By: Blocking:

Description

For forms on iOS with TextBoxes? and Mobile ScrollableViews? if a users attempts to move the cursor (magnifying glass) and moves off the current text line at all the cursor will jump to the end of the line when user ends their selection. This problem makes moving the cursor particularly difficult and frustrating as their sliding of their finger has to be precise. I noticed the problem more on short forms which were more likely to scroll/bounce.

I have attached a shorten version of the form attached to defect #18360. I used iOS simulator but also easily reproducible on actual devices. To reproduce, entered some characters in the text box. Touch and hold on the cursor to get into selection mode. In the process of trying to move the cursor to the left, move up or down enough to get the scrollbar to appear (you do not need to move far). You will notice even if you placed the cursor where you wanted it will a second later jump back to end of the line.

I did some debugging into this issue and noticed if I commented out line 574 in scrollable.js the issue was fixed but I am not 100% sure of the purpose of this line. I assume this line is here to handle any scrolling that may need to happen as a result of selection going outside the currently visible range.

Line 574: this.scrollTo(to);

This issue is related to defect https://bugs.dojotoolkit.org/ticket/18360 but did not solve it in all cases.

Attachments (1)

test_ShortFormLayout.html.zip (1.5 KB) - added by szerfas 5 years ago.

Download all attachments as: .zip

Change History (8)

comment:1 Changed 5 years ago by szerfas

Last edited 5 years ago by szerfas (previous) (diff)

Changed 5 years ago by szerfas

comment:2 Changed 4 years ago by dylan

Milestone: tbd1.11

comment:3 Changed 4 years ago by dylan

Priority: undecidedlow

comment:4 Changed 4 years ago by dylan

Milestone: 1.111.12

Ok, after massive triage, ended up with about 80 tickets for 1.11 and 400 or so for 1.12. That's a bit unrealistic, so first I changed all 1.12 to 1.13 (with the plan to move some forward to the new 1.12. Now, I'm moving some of the 1.11 tickets that are less likely to get done this month without help to 1.11. Feel free to help out in January if you want to see this ticket land in 1.11.

comment:5 Changed 4 years ago by Johannes Erk

This issue also affects our prodcut and has quite an impact on our mobile application in customer environments. A higher priority would be greatly appreciated!

comment:6 Changed 3 years ago by dylan

Milestone: 1.121.13

Ticket planning... move current 1.12 tickets out to 1.13 that likely won't get fixed in 1.12.

comment:7 Changed 2 years ago by dylan

Milestone: 1.131.14
Note: See TracTickets for help on using tickets.