Context menu change selection in table, which leaks to next cell
Reported by
m.sam...@cksource.com,
Aug 3 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: 1. Open this code snippet https://codepen.io/msamsel/pen/yoaRWP 2. Put cursor caret at the end of cell. After last letter in specific cell 3. Right click to open context menu You can also use just regular table, with some tools which investigate current selection. What is the expected behavior? Selection won't change, or selection remain inside this same cell What went wrong? Selection is enlarged, changed to range type and focusNode point to next cell. We had caret type selection inside one cell and this create range type selection with 2 cells. Did this work before? N/A Does this work in other browsers? No Behaviour is the same in Safari Problem doesn't exist on Firefox. Chrome version: 59.0.3071.115 Channel: n/a OS Version: OS X 10.12.6 Flash Version: It seems that problem is related to feature which automatically highlight and select word which is right clicked. Unfortunately here selection point to next cell what seems to be not ok. You can make this same type of selection if you put caret after last letter in cell, and then use Shift + Right Arrow to select next character. This will select 2 cells but not first character in next cell.
,
Aug 11 2017
,
Aug 21 2017
SelectionController::SelectClosestWordFromHitTestResult() failed to select word at <td>foo*</td><td>bar</td> where "*" denotes hit test position.
,
Sep 13 2017
Is there any progress on this? It's literally destroying table selection in CKEditor.
,
Sep 13 2017
Same thing happen in WebKit: https://bugs.webkit.org/show_bug.cgi?id=175131
,
Jan 10 2018
,
Jan 10
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by erikc...@chromium.org
, Aug 8 2017