iPad Can't Move Cursor in Visual Editor

[miqrogroove]

I've been ramping up iPad usage with WordPress both for mobility as well as testing.

The more I use it, the more frustrated I become with the visual editor. Due to what appears to be multiple bugs with both iOS and WordPress, I am often unable to move the cursor and must switch to the Text tab to do my editing.

When tapping into the Visual editor in a long post, the screen auto scrolls so that the cursor is sitting directly above the keyboard, and the admin bar moves to the middle of the page, covering most of the remaining editing area. This blocks the view of any preceing or following text, and makes it very awkward to write sentences longer than the editor is wide.

To move the cursor to a different part of the post, I have to un-focus the editor and the tap into the editor on a different line. The only place I can reliably land the cursor is at the end of a line, so to change anything in the middle of a paragraph, I have to use the text editor.

[miqrogroove]

Also, it is impossible to scroll up or down while typing because the iPad keyboard stops responding.

[SergeyBiryukov]

Related: #11489

[MikeHansenMe]

Related: #22519

[Ipstenu]

This seems to have been fixed by Apple. On iOS7 it's working

• Scrolling in a text box works
• Keeping text box active to click/move cursor works

That said, there are some iOS bugs that randomly causes your browser to change focus without warning, which is a pill, but it's iOS and not WP (Chrome devs were kvetching about that too).

Suggest close.

[miqrogroove]

I'm trying this now.

Not Fixed:

• After moving the cursor, cannot move cursor back to end of post.

Workaround:

• Moving focus to the Tags field enables me to re-focus the textbox with the cursor at end of post.

Fixed:

• Possible to scroll while typing.

At this point I would describe the post editor as barely usable. Being unable to continue the end of a post is a big problem for me.

[miqrogroove]

Please note this bug does not exist in the TinyMCE demo page. I do not agree with closing this ticket.

[azaozz]

Yeah, there seem to be quite a few problems with contenteditable in iOS Safari, and many are not being fixed or the fixes take years... Most seem caused by the onscreen keyboard. If it's closed all works somewhat better.

Not really sure if we can do anything to improve that. A good workaround for many of these problems is to force-close the keyboard, then open it again by tapping at the desired location.

[azaozz]

I believe all of these have been fixed in both TinyMCE 4.1 and iOS 8.1. Older versions of iOS may still experience some of the problems, unfortunately there is next to nothing we can do fix them there.

Closing as fixed (upstream). Feel free to reopen if some of these problems still exist and we can do anything to fix them.