WordPress does not function on iPad in View (non HTML Mode)

[Astriker]

I just thought I would pass on that I noticed when editing wordpress or creating blogs on the ipad browser, you cannot select the contect area of the body. It does not recognize it as a text field. I can select HTML and enter it there. This appears to be the only field that the safari browser does not identify as a field. May be apples problem, but passing along.

[nacin]

A bit late for 3.0. Moving to unassigned for now. I have a feeling this is a side effect of that it is a content editable space, and thus we can't do much about it.

[toscho]

The iPad ​doesn’t support contenteditable.

Maybe we could replace the element with a textarea after a check?

if(typeof(element.contentEditable) != 'undefined')
// modern content
else
// fallback

[jane]

Also, there is an iPad-native WordPress app.

[azaozz]

Although it doesn't look like it this is actually related to #13327. We can try to detect whether the browser doesn't have JS enabled or doesn't support other features needed by the editor and fall back to plain textarea with the proper filters applied.

Also perhaps the ipad browser will be updated to the full Safari functionality in the future.

[Astriker]

Replying to jane:

Also, there is an iPad-native WordPress app.

I am not aware of an iPad native, I am just using the current WP admin console that comes with it. It notices the Subject with no problem, only the area it does not. Is the iPad version app available or is it the iPhone version?

[dd32]

Also perhaps the ipad browser will be updated to the full Safari functionality in the future.

I somewhat doubt it'll happen anytime soon.

It would probably be best to disable TinyMCE for $is_iphone?

[nacin]

Replying to Astriker:
Is the iPad version app available or is it the iPhone version?

There is a WordPress for iOS app that works for iPhone, iPad, and iPod touch.

​http://iphone.wordpress.org

[astriker]

Replying to nacin:

Replying to Astriker:
Is the iPad version app available or is it the iPhone version?

There is a WordPress for iOS app that works for iPhone, iPad, and iPod touch.

​http://iphone.wordpress.org

I have the wordpress for iphone all setup, but I was hoping to use the full version in Safari, which is more of the iPad usage.

[simonwheatley]

TinyMCE release v3.3.4 addressed this (​http://tinymce.moxiecode.com/punbb/viewtopic.php?id=21314):

We also added detection logic for iPhone/iPad so that TinyMCE doesn't
get initialized on these devices. It's currently impossible for us to add
iPhone/iPad support since WebKit on these devices lacks any for of
caret within contentEditable areas. Even though this detection logic
will keep TinyMCE from being initialized it's recommended to do the
device checking on the server side since the main script of TinyMCE
will be loaded even though it can't be used.

I've created an incomplete patch which attempts to upgrade WP to TinyMCE v3.3.8, which is the current production release. Issues I've noticed with this patch:

• The spellchecker button is blank
• The align buttons don't work (error message: "TypeError: Result of expression 'c.editorCommands.mceJustify' [undefined] is not a function.")

Patch refinements welcome!

[azaozz]

Replying to simonwheatley:
TinyMCE will be upgraded to its latest version for WordPress 3.1, see #12574. I expect this will land in 3.1-alpha early in the next dev. cycle, probably early September.

Unfortunately that won't fix this issue completely. When editing a post we output the content slightly differently depending on whether the Visual or the HTML editor is loaded first. We should handle this in the back-end/PHP as the TinyMCE team suggests.

Patching this should be quite trivial, will add a proposed patch a bit later.

[simonwheatley]

Replying to azaozz:

Replying to simonwheatley:

Unfortunately that won't fix this issue completely. When editing a post we output the content slightly differently depending on whether the Visual or the HTML editor is loaded first. We should handle this in the back-end/PHP as the TinyMCE team suggests.

Patching this should be quite trivial, will add a proposed patch a bit later.

Fair enough. I think the patch needs $is_iphone to be global declaration at the top of the function... I'll post a patch shortly. Otherwise I've tested this on an iPad and it works, thanks!

Any chance we can get a nice small change like this into 3.0.1?

[simonwheatley]

Adds $is_iphone to the global declaration

[nacin]

(In [15460]) Disable the visual editor in iOS. props azaozz, simonwheatley. fixes #13326 for 3.1.

[nacin]

(In [15461]) Disable the visual editor in iOS. props azaozz, simonwheatley. fixes #13326 for 3.0.1.