CKEditor 4.0.1 does not load when user agent contains "mobile"

[Moritz Blume]

CKEditor 4.0.1 does not load when accessed from some browsers. I think this happens for any user agent containing the word "mobile". At least I could verify that from android ckeditor did not load, but when I switched to "desktop view" (which changes the android user agent imitating a desktop one), then ckeditor loads and is usable. The same happens when I use "user-agent switcher for chrome" under desktop chrome browser: when I choose iPhone or iPad, ckeditor does not load. But, for motorola xoom it loads (note that motorola xoom user agent does not contain "mobile").

[Moritz Blume]

Here is the code snippet that is responsible for this behaviour. If env.mobile is true, env.isCompatible is always false. I think that is a mistake, at least for android jelly bean CKEditor seems to work fine.

env.isCompatible = White list of mobile devices that supports.

env.iOS && version >= 534

!env.mobile && (

( env.ie && version > 6 ) ( env.gecko && version >= 10801 ) ( env.opera && version >= 9.5 ) ( env.air && version >= 1 ) ( env.webkit && version >= 522 )

false

);

[Jakub Ś]

Due to large amount of problems occurring in android browser, CKEditor was disabled in this environment until Android will 'standarazie' is browser to acceptable level.

@stoneweg could you perhaps share your experience in using CKE on your mobile device? To my understanding you have changed env.js and use CKE there. Such third-party input is very valuable to us.

[Anna Tomanek]

Android is not a supported environment (yet) and support for mobile environments is so far limited to a list of specific white-listed ones. You can change these settings to accept any mobile environment (at your own risk), but you might not get the same experience that you are getting for desktop environments.

We aim to have CKEditor work on Android devices, too, so if you are willing to use it, you will be most welcome to report any bugs that you find. At the moment it is not exactly the case that "CKEditor seems to work just fine", there are problems with selecting, deleting, some plugins etc.

[Moritz Blume]

IMO a not perfectly working editor is better than no editor at all. I see that you guys have very high expectations for CKEditor, which is perfectly fine. But it would be good to at least provide an option to configure CKEditor to work with android, for those people who think they can risk offering it to their users. Having to dig into the source code to find this is hacky and time consuming. So in this sense I think this is still a bug, maybe more a documentation/configuration.

[Anna Tomanek]

Well, yes and no. You've got a point that we could possibly inform the developers that Android support is disabled for a purpose and that they can change it.

However, we are very reluctant to do so since the reality is that for every single developer who understands what "at your own risk" is, there will be twenty unexperienced ones who will start threads on the forum, report tickets, and flood us with e-mail stating that we should fix it ASAP, because "what should work does not work".

On a positive note, though, we are now checking whether we will be able to fix some contenteditable bugs/ work around them until Google provides support from their side. If it turns out we are able to get the most important features to work, Android support will come to CKEditor as well. Please note that for CKFinder it is already supported, so it's not like we don't care.

If you are willing to test it a bit and report your findings, it will be much appreciated and will definitely speed up the process. See the ​Android keyword for a list of bugs that are currently open (more are coming).

[Moritz Blume]

Ok thanks a lot for that feedback, I will file bugs under the android keyword then once I start the testing of my website.

[Jakub Ś]

#10486 was marked as duplicate.

[Jakub Ś]

#12355 was marked as duplicate.