Make WordPress Core

Opened 8 years ago

Closed 4 years ago

#32502 closed defect (bug) (worksforme)

Cannot advance the cursor through input fields on iOS

Reported by: ryan's profile ryan Owned by: valentinbora's profile valentinbora
Milestone: Priority: high
Severity: major Version:
Component: Administration Keywords: 2nd-opinion needs-testing close make-flow
Focuses: ui, administration Cc:


On iOS devices, I can’t advance the cursor through text that lies beyond the bounds of the Title input. The cursor stops advancing through text once it hits the left or right border of the input field. This causes me to abandon my mobile session and pick up editing when I get to a laptop. Mobile abandonment of edit flow is not good.

This happens on all my iOS devices. Android looks good.

Change History (26)

This ticket was mentioned in Slack in #core-editor by boren. View the logs.

8 years ago

#2 @ryan
8 years ago

  • Priority changed from normal to high
  • Severity changed from normal to major

This ticket was mentioned in Slack in #core-flow by boren. View the logs.

8 years ago

#4 @designsimply
8 years ago

Tested and confirmed with the following steps to reproduce:

  1. Go to Posts > Add New on any iOS device
  2. Type a title long enough to fill the title input field and then some
  3. Try to move the cursor to the beginning of the title

Result: I'm stuck and can't advance the cursor beyond the last text I typed in the field. 52s

Tested with WP 4.3-alpha-32280-src on Safari iOS 8.3 with an iPhone 6.

Last edited 8 years ago by designsimply (previous) (diff)

#5 @designsimply
8 years ago

  • Summary changed from Cannot advance the cursor through the Title input field on iOS to Cannot advance the cursor through input fields on iOS

#6 @designsimply
8 years ago

Tested a few other input fields, and the same problem happened for all of them:

  1. Captions when creating a gallery
  2. The "Name" field on the Posts > Category page
  3. The post slug when editing a draft
  4. "Site Title" field in Settings > General
  5. etc.

It appears all the input fields have the same problem.

#7 @ryan
8 years ago

  • Keywords ios mobile added
  • Milestone changed from Awaiting Review to 4.3
  • Version set to 4.2.2

This ticket was mentioned in Slack in #core-flow by boren. View the logs.

8 years ago

#11 @ryan
8 years ago

  • Keywords mobile-abandonment added

#12 @iseulde
8 years ago

Not sure if there's anything we can do about an iOS bug.

This ticket was mentioned in Slack in #core by boren. View the logs.

8 years ago

This ticket was mentioned in Slack in #core by obenland. View the logs.

8 years ago

#16 in reply to: ↑ 13 @obenland
8 years ago

  • Milestone changed from 4.3 to Future Release

Set to be fixed in a future release, unless we find a cure before 4.3 ships.

#17 @azaozz
8 years ago

As far as I see the only way to work around that super annoying iOS bug is to replace <input type="text"...> with <textarea>. Then these fields will be vertically scrollable and we could also set the height from JS when the string is too long to fit.

That might work in a few places like the post title, unfortunately no way to do it everywhere.

#18 @obenland
8 years ago

That sounds like a really bad hack.

#19 @azaozz
8 years ago

Yeah, if we do it only for iOS it will be pretty hacky.

On the other hand a textarea for the post title works pretty well in all browsers and viewport sizes. It is still a bit annoying to have to select the text and drag to reveal the rest of it when the title is too long to fit. If we have a textarea there it will reveal the whole text (of course scrollbars should be off in all cases).

#20 @johnbillion
8 years ago

  • Version 4.2.2 deleted

This sounds like a pretty fundamental bug on iOS. Is there anything WordPress-specific about it? Are there any text inputs that are not affected? If so, what is it about them that means they are not affected? As Ryan mused, Is this really broken across the entire mobile web on iOS 8?

Swapping out text inputs for textareas to get around this bug is unacceptable.

As much as I hate to say it, this looks like a wontfix unless someone comes up with a better fix.

#21 @iseulde
8 years ago

  • Component changed from Editor to General
  • Milestone changed from Future Release to Awaiting Review

#22 @DrewAPicture
8 years ago

  • Component changed from General to Administration

#23 @iseulde
8 years ago

iOS 9.2 and this is still an issue...

#25 @valentinbora
4 years ago

  • Focuses ui administration added
  • Keywords 2nd-opinion needs-testing added; make-flow ios mobile mobile-abandonment removed
  • Milestone set to 5.4
  • Owner set to valentinbora
  • Status changed from new to accepted

For my feeling, this is no longer an issue on iOS 13.3.1, tested on both Chrome and Safari. Please give it a try.

#26 @valentinbora
4 years ago

  • Keywords close added

#27 @SergeyBiryukov
4 years ago

  • Keywords make-flow added
  • Milestone 5.4 deleted
  • Resolution set to worksforme
  • Status changed from accepted to closed

Closing per comment:25, feel free to reopen if there's still an issue.

Note: See TracTickets for help on using tickets.