mzslater wrote:Has anyone gotten FCKeditor or CKeditor to work on an iPad?
Any insights into what it will take?
CKEdtior works fine on iPAd, the only problem I get is that the onscreen keyboard on iPad doesn't popup automatically when the editor is focused and there is no way to call the onscreen keyboard manually
ahmadabuomar wrote:lol I am sorry, I meant to say that it shows ok but I can't type, do you have any idea on how to fix this?
You just have to wait for Apple to release a version of Safari that behaves like the desktop version. You can write Steve Jobs about it because no one outside Apple can help with that problem (in other systems it could be possible to use another browser, but that's ruled out in iPhoneOS)
Looks like Safari isn't interpreting the editor field as a form input, so it's not triggering the keyboard. You may be able to verify this by selecting another form field on the page and seeing if you can hit 'Next' or 'Previous' to tab to CKEditor? Alternatively, I think Opera Mini is available, you could give that a try?
EDIT: Just given that a try on my phone and it doesn't work Although, it was the first time I'd bothered looking at the HTML produced by CKEditor, and now I know why the keyboard doesn't popup - there's no actual form elements involved when you edit, so it is just a Javascript error with Safari on iOS. Which hopefully means it can/will be fixed
EDIT 2: I'm being slow this morning, apologies! I just checked it out and of course the quickest and simplest fix is to hit 'Source' view - this creates a <textarea> which you can edit without a problem It's not WYSIWYG, but it's editable!
b3n wrote:Looks like Safari isn't interpreting the editor field as a form input, so it's not triggering the keyboard. You may be able to verify this by selecting another form field on the page and seeing if you can hit 'Next' or 'Previous' to tab to CKEditor? Alternatively, I think Opera Mini is available, you could give that a try?
EDIT: Just given that a try on my phone and it doesn't work Although, it was the first time I'd bothered looking at the HTML produced by CKEditor, and now I know why the keyboard doesn't popup - there's no actual form elements involved when you edit, so it is just a Javascript error with Safari on iOS. Which hopefully means it can/will be fixed
EDIT 2: I'm being slow this morning, apologies! I just checked it out and of course the quickest and simplest fix is to hit 'Source' view - this creates a <textarea> which you can edit without a problem It's not WYSIWYG, but it's editable!
My reading of that documentation indicates that mobile Safari simply can't send text data to a contenteditable element in a page -- in other words, there's no way to put text into the CKEditor edit area, even if you could force the browser to bring up a keyboard. CKEditor would need to use a textarea element (which is why it works when you're in "Source" mode, since that's a genuine textarea) but that won't allow arbitrary non-text elements like embedded images, etc.
It might be possible to have a kind of hobbled styled-textarea middle ground that allowed styling of text in a WYSIWYG manner but not arbitrary image insertion or Flash objects or whatever... but that would be a lot of effort for something Apple should really just fix on their end.
Yes, from the start it's clear that the problem is the lack of support by Apple. Also, you must remember that iPhoneOS doesn't support Flash, so inserting them into the editor would be the minor of your problems.
And as Mozilla has shown with Fennec for Android, it's possible to provide contentEditable in a mobile device, so in the long term it might be better to wait a little to check what's provided in tablets with Android before rushing to get an iPad if you really want to use it with any web page.
My reading of that documentation indicates that mobile Safari simply can't send text data to a contenteditable element in a page -- in other words, there's no way to put text into the CKEditor edit area, even if you could force the browser to bring up a keyboard. CKEditor would need to use a textarea element (which is why it works when you're in "Source" mode, since that's a genuine textarea) but that won't allow arbitrary non-text elements like embedded images, etc.
It might be possible to have a kind of hobbled styled-textarea middle ground that allowed styling of text in a WYSIWYG manner but not arbitrary image insertion or Flash objects or whatever... but that would be a lot of effort for something Apple should really just fix on their end.
I'd like to thank B3N for his suggestion to use the source view. I was able to get that working so that iPad users can at least use our site. I removed everything from the toolbar for iPad users and defaulted it the Source view with the code I found on this site:
<script type="text/javascript"> function FCKeditor_OnComplete(editorInstance) { // Switch the editor from WYSIWYG to SOURCE on startup. editorInstance.SwitchEditMode(); }
</script>
Hopefully, Apple will get their act together and let others get their work done!
That's exactly what i am going to do, wait... i have to deliver a website for some 300 membres that Will receive an iPad, maybe the Samsung tablet is more appropriate for business!!!
I just got an Ipad and was wondering where i could get it to function as it would on my computer.. i mean, is there an app to fetch from the app store?
I wanted to report something that changed for me in Apple iOS's support of ckEditor. It's a small change technically, but significant for me.
I use Mindtouch wiki software that uses ckEditor to edit pages. Up to this point I could view pages on my iPhone / iPad; but never edit them. Very limiting!!! Having submitted bugs to Apple and periodically checking the iOS release I had a surprise. After I upgraded to iOS 4.3.2 last weekend I noticed that:
1) When I went into edit mode on a wiki page, the iOS keyboard popped up! It NEVER did this before. So it's recognizing the text as an "editable area" and treating it as such.
2) When the page re-renders in edit mode it puts me in HTML view of the content. This also didn't happen before. Mindtouch always presents the ckEditor toolbar first. You have to hit an explicit "view as html" command to modify the source. I'm grateful it knows to default here instead.
I attribute this to a change in iOS Safari implementation (haven't reinstalled Mindtouch in a while). Has anyone else noticed this? The net effect is I can edit!!! I've only checked this periodically so I can't say 4.3.2 is the exact version the change was implemented but I'm a VERY happy camper now. Content editing!!!
In closing, I realize I'm celebrating the ability to edit raw HTML on a site dedicated to avoiding the need for that alltogether People devote time and enthusiasm to ckEditor so WYSIWYG editing can happen with a toolbar, buttons, and the whole shebang. Apple is still not supporting this completely. I hope, however, this iOS Safari change is a step in that direction. Doing what I can to support that progression.
many thanks for reporting progress on this annoying issue, we really *are* glad to see at least partial editing support on Apple's side. Since this lies entirely in the hands of Apple, it really is the users' pressure that can make them implement the changes necessary for CKEditor to work in the WYSIWYG mode, with all its cool features and possibilities.
Thanks for your support and let's keep our fingers crossed for the complete WYSIWYG editing support in Apple products!
I'm sorry, I'm a little confused as to where things stand with CKEditor and the iPad. I see that in CKEditor 3.2.1 that ticket #5440 was included and was supposed to mark mobile browsers as incompatible. So if I get the current version of CKEditor (3.6), will an iPad user see an HTML textarea, or will they be completely unable to do any editing at all?
Re: iPad support
Re: iPad support
Re: iPad support
Re: iPad support
Re: iPad support
You just have to wait for Apple to release a version of Safari that behaves like the desktop version. You can write Steve Jobs about it because no one outside Apple can help with that problem (in other systems it could be possible to use another browser, but that's ruled out in iPhoneOS)
Re: iPad support
Looks like Safari isn't interpreting the editor field as a form input, so it's not triggering the keyboard. You may be able to verify this by selecting another form field on the page and seeing if you can hit 'Next' or 'Previous' to tab to CKEditor? Alternatively, I think Opera Mini is available, you could give that a try?
EDIT: Just given that a try on my phone and it doesn't work Although, it was the first time I'd bothered looking at the HTML produced by CKEditor, and now I know why the keyboard doesn't popup - there's no actual form elements involved when you edit, so it is just a Javascript error with Safari on iOS. Which hopefully means it can/will be fixed
EDIT 2: I'm being slow this morning, apologies! I just checked it out and of course the quickest and simplest fix is to hit 'Source' view - this creates a <textarea> which you can edit without a problem It's not WYSIWYG, but it's editable!
Re: iPad support
Re: iPad support
It seems as though the problem runs a lot deeper than just a missing keyboard:
http://developer.apple.com/safari/libra ... E_ELEMENTS
My reading of that documentation indicates that mobile Safari simply can't send text data to a contenteditable element in a page -- in other words, there's no way to put text into the CKEditor edit area, even if you could force the browser to bring up a keyboard. CKEditor would need to use a textarea element (which is why it works when you're in "Source" mode, since that's a genuine textarea) but that won't allow arbitrary non-text elements like embedded images, etc.
It might be possible to have a kind of hobbled styled-textarea middle ground that allowed styling of text in a WYSIWYG manner but not arbitrary image insertion or Flash objects or whatever... but that would be a lot of effort for something Apple should really just fix on their end.
Re: iPad support
And as Mozilla has shown with Fennec for Android, it's possible to provide contentEditable in a mobile device, so in the long term it might be better to wait a little to check what's provided in tablets with Android before rushing to get an iPad if you really want to use it with any web page.
Re: iPad support
Re: iPad support
Just took a short look at this, but I believe this is the direction Apple wants you to go in.
http://developer.apple.com/safari/libra ... TP40009977
A Safari Extension has it's own Javascript API
Re: iPad support
Hi,
I'd like to thank B3N for his suggestion to use the source view. I was able to get that working so that iPad users can at least use our site. I removed everything from the toolbar for iPad users and defaulted it the Source view with the code I found on this site:
<script type="text/javascript">
function FCKeditor_OnComplete(editorInstance) {
// Switch the editor from WYSIWYG to SOURCE on startup.
editorInstance.SwitchEditMode();
}
</script>
Hopefully, Apple will get their act together and let others get their work done!
Thanks again!
Ember
Re: iPad support
Re: iPad support
Re: iPad support
Re: iPad support
I try to figure it now.
anyone have suggestion for this?
Re: iPad support
I have the same problem,I just got my Ipad and try to get FCKeditor or CKeditor to work on an iPad,I hope to get some solutions
Re: iPad support
I wanted to report something that changed for me in Apple iOS's support of ckEditor. It's a small change technically, but significant for me.
I use Mindtouch wiki software that uses ckEditor to edit pages. Up to this point I could view pages on my iPhone / iPad; but never edit them. Very limiting!!! Having submitted bugs to Apple and periodically checking the iOS release I had a surprise. After I upgraded to iOS 4.3.2 last weekend I noticed that:
1) When I went into edit mode on a wiki page, the iOS keyboard popped up! It NEVER did this before. So it's recognizing the text as an "editable area" and treating it as such.
2) When the page re-renders in edit mode it puts me in HTML view of the content. This also didn't happen before. Mindtouch always presents the ckEditor toolbar first. You have to hit an explicit "view as html" command to modify the source. I'm grateful it knows to default here instead.
I attribute this to a change in iOS Safari implementation (haven't reinstalled Mindtouch in a while). Has anyone else noticed this? The net effect is I can edit!!! I've only checked this periodically so I can't say 4.3.2 is the exact version the change was implemented but I'm a VERY happy camper now. Content editing!!!
In closing, I realize I'm celebrating the ability to edit raw HTML on a site dedicated to avoiding the need for that alltogether People devote time and enthusiasm to ckEditor so WYSIWYG editing can happen with a toolbar, buttons, and the whole shebang. Apple is still not supporting this completely. I hope, however, this iOS Safari change is a step in that direction. Doing what I can to support that progression.
Re: iPad support
many thanks for reporting progress on this annoying issue, we really *are* glad to see at least partial editing support on Apple's side. Since this lies entirely in the hands of Apple, it really is the users' pressure that can make them implement the changes necessary for CKEditor to work in the WYSIWYG mode, with all its cool features and possibilities.
Thanks for your support and let's keep our fingers crossed for the complete WYSIWYG editing support in Apple products!
Documentation Manager, CKSource
See CKEditor 5 docs, CKEditor 4 docs, CKEditor 3 docs, CKFinder 3 docs, CKFinder 2 docs for help.
Visit the new CKEditor SDK for samples showcasing editor features to try out and download!
Re: iPad support
Richard
Re: iPad support
I'm sorry, I'm a little confused as to where things stand with CKEditor and the iPad. I see that in CKEditor 3.2.1 that ticket #5440 was included and was supposed to mark mobile browsers as incompatible. So if I get the current version of CKEditor (3.6), will an iPad user see an HTML textarea, or will they be completely unable to do any editing at all?
Re: iPad support