iOS5 Support

Can you confirm that the basic tests that I did in Android ( http://alfonsoml.blogspot.com/2010/12/l ... 3-for.html ) are passing correctly in iOS5?

And is the behavior correct in both iPhones and iPads or only iPads?

If the caret and selection functionality now work correctly then it could be possible to set the iOS5 browser as a supported one, but if it's too buggy ...
BTW, does <input type="file"> work or is it still unsupported?

So what are the answers?

Does iOS really support the features needed by the users like showing the keyboard and allowing to select text?
(keep in mind that they might claim that contentEditable is supported because the commands to turn text bold and the like work, but that's not so important for CKEditor compared with the ability to write content).

You don't need any skill. Just some iOS device to test.

Load the http://alfonsoml.blogspot.com/2010/12/l ... 3-for.html page and read what I tested. Check how it works in a normal desktop browser.

Now use the iOS device and try to type, select text, click on that link. Just what an user would do. And then report back if those features work or not.

And what does that mean with regards to the tests themselves?

You have an iOS5 device right?
then load that page and try to type in the part that says "Type here.., a link (it's part of the content, so it shouldn't be active)"
Do you get the keyboard?
Do you see the caret?
Can you move the caret through the contents?
Can you select some of that text?
What happens when you click/touch the link?

It should take you 1 minute to test and maybe 2 to write back the results. Or do you expect someone else to buy an ipad and upgrade to iOS5 just to do the basic tests and check if it's feasible to enable it as a supported browser?

@webjive - Your help in testing mobile devices would be more than appreciated. So far Apple totally ignored WYSIWYG editors (providing no support for contenteditable elements), that's why Alfonso was sceptical about it.

As we all know testing software on iOS is a bit troublesome, so if you'd be willing to check the new iOS5 and report us your findings that would be great.

As Alfonso suggested, you could test first a plain contenteditable element (e.g. the one here: http://alfonsoml.blogspot.com/2010/12/l ... 3-for.html) and after getting a successfull result,
try CKEditor (you may need to adjust CKEDITOR.env.isCompatible first to enable CKEditor on mobile devices, to do it you can use a patch from http://dev.ckeditor.com/ticket/6089).

Even if we don't start working on it immediately, knowing exactly how far we are at this moment from supporting this environment, would definitely help us.

Hi,

The previous poster does not seem to be understanding that you want him to run the tests and get back to you - I also have a developer account as well as having IOS5 beta, *but* I do not have a device to run it on, instead I use the emulator.

Here are the answers to your questions:

First test: I click on the div, no carat appears.

Second test: I do not understand your test. There is no trackball on any mobile device. Since I cannot make a selection within the div to cause a carat to appear scrolling simply scrolls the entire window.

Third Test: Clicking on the link tries to open it.

Fourth Test: Keyboard does not appear.

Firth Test: As noted above keyboard does not appear, no way to complete this test.

Sixth Test: I do not know what Swiftkey is.

Seventh Test: This is a comparison with Android, I do not have android.

Please note that I can perform additional tests on demand, please email me and I can run them.

Again, I have an emulator, not an IOS5 device, but they behave very similarly.

Finally I have played with TinyMCE as well, and there is no evidence that it is working there either.

Thanks for your feedback.

I find it strange that you can't get the keyboard because that's the very first point in order to allow users to edit the content, and according to some posts other people have stated that it's working with iOS5, maybe a glitch with the emulator?

The rest of the tests doesn't make too much sense if the user can't edit the contents, but just for clarity:
There are mobile devices with trackballs, one example is my Nexus One. Of course, not all the devices have such feature, but it's up to the OS to provide a way to move the caret that the user can easily understand, usually clicking on another point should be enough, but I find the trackball very useful to move a few chars back to adjust something.

Likewise, creating a selection is an OS thing, I would expect it to be similar to the way to copy text from a normal page. The test should be stated as: is it possible to somehow select part of the content?

Swype is an alternate keyboard for Android, in Android the user can switch to different keyboards with better prediction, support for several languages at once, blind typing, etc... it's up to the user the option to search and use one that fits his preferences.

Hi,

The emulator itself is pretty good for testing application behavior, but I've found it to be subpar for testing browser behavior. There are a number of behaviors that don't map, for example gestures. You cannot simulate gestures using the emulator, even with the mouse. For example holding your finger down and moving it from the left to the right... very poor support in the emulator.

Given that, I would have expected the load events to work properly, and they did not.

One problem here is that if you upgrade a device to IOS5, you can not go back to IOS4, so I unfortunately cannot update my phone, which I believe is what the prior user was discussing.

Apparently there is a way to provision an external iPhone/ipad/itouch with IOS5 remotely, so in theory if you were to provide your UUID I could add your device to my list, send you the firmware, and you could update.

Do you guys have iPhones? I don't see why you care about nexus one or other devices. Android and iPhone make up a substantial majority - as such most of the developers who use this tool are interested in support there specifically, myself included.

Please let me know if you would like other tests run. If I get an IOS5 device I will follow up here.

thanks,
Kevin

The Nexus (one and S) are the Google branded developers devices for android.

UPDATE

The new version IOS5 Beta 5 was released today. I loaded up my simulator, browsed over to tinymce.com and... it works! Finally progress.

I reanswer all the above questions below:

First test: I click into the div testing area, a carat appears exactly where I click.

Second test: Scrolling with trackball - no IOS device currently has a trackball. Scrolling causes the page to scroll.

Third test: Clicking on the link does not cause the link to open. The carat moves to either the right or the left side of a link word depending on which side your click was closest to. The carat behavior is seemingly the same as if the link was regular text, as it does not let you easily move the carat into the middle of a word.

Fourth test: Upon clicking within the div the keyboard popped up, as one would expect.

Fifth test: Keyboard works very nicely, not slow at all.

Sixth test: Swiftkey does not apply to IOS

Seventh test: I tried modifying my code so that CKEditor would load under IOS, but I could not figure out how to do it. Instead just regular textarea appears.

Please follow up with additional tests so we can see what's involved to get proper support. This sucks that TinyMCE has this and CK doesn't, I need this

Anyone interested can test now CKEditor under iOS 5 with these demos: http://nightly.ckeditor.com/

if you prefer to test locally you can download the current build, but remember that it's not usually aimed at production sites (although currently the code is quite stable and there are only a few changes since 3.6.1, but if you read these message 3 months from now the situation can be quite different)

Your given blogs links are really helpful. Thanks