Skip to Content

Will iOS 5's Safari deliver better support for web editors?

One of the long-standing frustrations for anyone who's tried to edit blog posts or web documents using Mobile Safari is the absence of support for the HTML5 contentEditable attribute. The attribute, which began as an Internet Explorer 5.5 feature and later found its way into most modern browsers, is part of the suite of tools that made it possible for older versions of Google Documents and other inline editors to do their rich-text WYSIWIG editing magic.

[Commenter Darren notes that Google Docs itself does not use contentEditable anymore, but instead does all the editing using a custom JavaScript editor. –MR]

Unfortunately, up through iOS 4.3 there's no support for the contentEditable attribute in Mobile Safari, which means that popular web editing tools either don't work at all or have to provide severely limited iOS-specific versions. According to this thread on Hacker News, it looks like things may be changing in iOS 5; preliminary tests on the beta seem to show that the attribute is working as expected in the new version of Safari.

If this does prove out for the final builds of iOS 5 (and that's a reasonably substantial 'if,' since we're still several months away from release), we could be looking at a dramatic improvement in support for virtually all web-based rich text editing tasks on the iPad. For those of us who have struggled with this issue for a while, it's welcome news indeed.

Thanks to Gary Poster for his question.



Categories

iOS

One of the long-standing frustrations for anyone who's tried to edit blog posts or web documents using Mobile Safari is the absence of...
 

Add a Comment

*0 / 3000 Character Maximum Comment Moderation Enabled. Your comment will appear after it is cleared by an editor.

3 Comments

Filter by:
spinthisdj

I'm still waiting for Apple to provide input type="file" support. Don't tell me it's because Apple doesn't want to give access to the file system... of course they don't but they could easily give access to an API that lets users select. say, a vcard for contacts or a photo/video from the camera roll.

June 09 2011 at 12:45 PM Report abuse rate up rate down Reply
Darren

Actually, I don't think Google uses contenteditable for Google Docs anymore. It's pretty inconsistent cross-bowser from what I understand. http://googledocs.blogspot.com/2010/05/whats-different-about-new-google-docs.html

June 09 2011 at 11:24 AM Report abuse rate up rate down Reply
Chris Nurre

I've been following the iOS and contentEditable issues and last I checked Android browsers didn't support contentEditable either. That maybe have changed in the last month or so. The reason I've been following was primarily because I really wanted to use iEtherpad which is based on https://github.com/ether/pad.

Hopefully this is true and we can use text editors on iOS!

June 08 2011 at 9:48 PM Report abuse rate up rate down Reply
painted_dog

.. just curious, does Android's browser allow for the contentEditable attribute?

June 08 2011 at 9:32 PM Report abuse rate up rate down Reply
Buy an ad here

Tweets

© 2012 AOL Inc. All Rights Reserved.