Opened 12 years ago
Closed 12 years ago
#9752 closed Bug (wontfix)
Text selection via Shift+Arrows doesn't expand over multiple cells in backward direction
Reported by: | Vladimri S. | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | Core : Selection | Version: | 4.0 Beta |
Keywords: | Firefox | Cc: |
Description
Browser: Firefox 16.0.2 (if relevant)
It appears, that CKEditor handles selection over multiple cells in tables in two ways:
- Selecting by mouse: whole cells are being selected.
- Selecting by Shift+Arrows: text in cells is being selected.
There's an issue regarding the second way. This type of selection expands finely over multiple cells, but only when we move forward, i.e. use Shift+RightArrow and Shift+DownArrow to select.
This type of selection does not expand over multiple cells in backward direction, i.e. when we use Shift+LeftArrow.
Assume we start selecting text from the middle of a cell and go backwards. When selection's "tail" (it's "growing" part) reaches beginning of the cell, it occasionally swaps with selection's "head" (it's "stationary" part) and so pressing Shift+LeftArrow further will just make our selection shrink in backward direction.
Selecting over multiple cells with Shift+UpArrow causes some other effect: the behaviour is more or less what we expect it to be - selection is spanned over multiple cells to the point in the upper row, that closely corresponds to our starting position, but we can make it only once. Any attempt to press Shift+UpArrow once more will just reset our selection.
i.e. Version is actually CKEditor 4.0 (revision 769d96134b). I just can't find it in the drop-down list below.
Change History (1)
comment:1 Changed 12 years ago by
Keywords: | Firefox added; selection tables removed |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
If you use plain HTML page that has contenteditable="true" you will notice that this works the same way. No editor logic and same behaviour.
In short this is how browser handles it and there rather nothing we can do about it.
NOTE: this may also have to do with system and browser locale. What I’m trying to say is that computer and browser with rtl language may get opposite behaviour.