In the last version of iOS, support for contentEditable was enabled so CKEditor works again. However it is disabled through Sakai with a check on a session attribute
Ideally we'd still want to clean up WURFL for 2.9 and fix that (
SAK-21334) but I'm not sure if we need another property to indicate that we still want to be on the mobile portal but not replace the CKEditor, or if it can some how be accomplished with just this one? And can mobileESP say if the device supports contentEditable or will we just have to go based on the userAgent? In that case we might want to use a property to define acceptable user agents.