Description: Sometimes, when you have a vertically merged cell in a table and you position the insertion point on the first row and press <down>, the insertion point does not go down. Notes: * This happens all the time for me in one particular table where I have repeatedly merged and split cells (see attachment); the misbehavior persists when the table is copied to a new document. It does not happen in a new table. * Other types of navigation, including <up> and <right> work fine. Steps to Reproduce: Open attached document. Go to merged cell and press <down>. Actual Results: Nothing happens. Expected Results: Insertion point should move to the second row. Reproducible: Sometimes User Profile Reset: No Additional Info: Version: 6.4.5.2 (x64) Build ID: a726b36747cf2001e06b58ad5db1aa3a9a1872d6 CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded
Created attachment 170310 [details] Document which demonstrates issue
I can confirm it, but I also think, that there is something wrong with the table cells. If you put curso in one of the cells, it seems, that the cursor is misplaced. And I also couldn't select the whole text. Do you get the same result? How have you created the table? => NEEDINFO
(Responding to comment 6) If I attempt to place the cursor on the second row, it is misplaced: it shows up at the same X position, but on the first row. I am unable to select all the text (in a cell, which is my interpretation of what you meant) with the mouse, due to the positioning issue referenced above. However, I can select all the text with <Ctrl+A> or by starting at the beginning and using <Shift+Right> to move to the end. I created the table with an ordinary Table / Insert Table command. However, I have been editing the table for a long time, with many instances of Table / Merge Cells and Table / Split Cells. I would not be able to provide a reproducible sequence of steps to repeat the corruption; I'm hoping that the internal structure of the document will reveal clues.
(In reply to Alan Frank from comment #3) > I created the table with an ordinary Table / Insert Table command. However, > I have been editing the table for a long time, with many instances of Table > / Merge Cells and Table / Split Cells. I would not be able to provide a > reproducible sequence of steps to repeat the corruption; I'm hoping that the > internal structure of the document will reveal clues. So I think this is not a general problem, but a problem of a very specific table. And since it is not possible to reproduce the steps of creating this table, it will impossible to narrow down to the original problem. So i close the bug. Feel free to change it back to UNCONFIRMED with a short reasoning, if you disagree. => RESOLVED INSUFFICIENTDATA