Opened 10 years ago
Last modified 9 years ago
#12457 confirmed Bug
[iOS 8 Safari] Selection issues while typing
| Reported by: | arshdeeps86 | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | General | Version: | |
| Keywords: | iOS8 Safari8 | Cc: |
Description
I am developing an iOS app which integrates ckeditor 4.4.4. I just started testing on iOS 8, seems like ckeditor does not work at all. Whenever i have more than 500 words in a document,the following issues occur:
- Focus keeps on switching between caret current position and top of page. Sometimes caret is also moved to the top of page while i am typing.
- Touch event does not work when document is long, so i cannot start typing.
- Cannot scroll my content -- happens randomly.
I have tested on nightly build 4.4.5 also. Issues can be reproduced in that build also. Seems like these are due to toolbar validation because if open my document in read only mode, none of the issues. occur. Any ideas on the fix? In the mean time any way i can disable the toolbar and still work in wysiwyg mode?
Change History (8)
comment:1 Changed 10 years ago by
| Keywords: | iOS8 added; iOS 8 selection removed |
|---|---|
| Status: | new → confirmed |
| Version: | 4.4.5 (GitHub - master) |
comment:2 Changed 10 years ago by
| Keywords: | Safari8 added |
|---|
comment:4 Changed 10 years ago by
I tested this with native contenteditable (both inline and iframe) and it works.
comment:5 Changed 10 years ago by
The fact that native contenteditable behaves better (although, in few minutes I found bugs on it too) is not a proof that we can make CKEditor working, because CKEditor uses also APIs which may be broken.
comment:6 Changed 9 years ago by
I just ran into the issue 1 (sudden scroll/jump to top while typing). While I was trying to get around it, I found out that it can be prevented by space pressed after each letter. This is naturally not usable at all, but perhaps might help someone more knowledgable to find what's going on. Also it seems to be related to the onscreen keyboard, because it does not happen with bluetooth keyboard connected.
comment:7 Changed 9 years ago by
Seems like only way to get it working on iOS is by using divearea plugin. I have been using it quite a while now. No issues so far.
I can confirm the same issues and much more... Safari on iOS8 seems to be very broken or at least very incompatible with its previous versions. And it seems to be very slow comparing to iOS7 too ;/
I don't know if we can do anything, but we definitely must try.