Opened 10 years ago
Last modified 8 years ago
#13593 review Bug
[iOS, Android, WP] Fire editor#selectionChange on selection changes caused by touch events — at Version 3
| Reported by: | Piotrek Koszuliński | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | General | Version: | |
| Keywords: | iOS Android NiceToHave | Cc: |
Description (last modified by )
Currently editor#selectionChange is based on:
- native selectionchange,
- keyboard events,
- mouse events.
Therefore, CKEditor does not know about selection changes done on touch devices if browser does not implement selectionchange itself. It may also happen that we have some bugs in this system.
Lack of editor#selectionChange and checkSelectionChange() calls result in various issues like wrong selection being locked on focus (we store a reference to the last selection) and lack of updates in commands states. I think that related tickets may be:
Change History (3)
comment:1 Changed 10 years ago by
| Status: | new → confirmed |
|---|---|
| Summary: | Fire editor#selectionChange on selection changes caused by touch events → [iOS, Android] Fire editor#selectionChange on selection changes caused by touch events |
comment:2 Changed 9 years ago by
| Milestone: | CKEditor 4.5.3 → CKEditor 4.5.4 |
|---|
comment:3 Changed 9 years ago by
| Description: | modified (diff) |
|---|---|
| Summary: | [iOS, Android] Fire editor#selectionChange on selection changes caused by touch events → [iOS, Android, WP] Fire editor#selectionChange on selection changes caused by touch events |
Note: See
TracTickets for help on using
tickets.
