Description: Following deletion of almost all the cells in a column with selected context >right click>delete>shift cells up, the cells which have filled the void are not fully selectable with ctrl+shft+cursor down. Steps to Reproduce: In the attached .ods focus E2 Ctrl+shft+cursor down 3 times to select the entire column leaving E1 unselected Right click the selected cells and from the context menu >Delete From the delete cells panel confirm Shift Cells Up Select the scroll button from the bottom right and "slide" it to the top of the page Focus E1 Ctrl+shft+cursor down to select the entire column The Scroll Button now indicates there are far fewer cells in the column. It is possible to continue sliding the scroll button down and its visual representation does diminish with each effort but it might take a long time to get to the bottom Actual Results: Incorrect representation of and access to the entirety of cells in the column Expected Results: Access to all cells in the column Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.0.6.2 (x64) Build ID: 144abb84a525d8e30c9dbbefa69cbbf2d8d4ae3b CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: sv-SE (en_GB); UI: en-GB Calc: threaded
Created attachment 173909 [details] Simple demonstration .ods
The behaviour is the same as with any blank file when you select the whole column either starting from the first row or clicking the column header. It scrolls to the bottom whenever you start the selection from some other row than the first with ctrl-shift-down. So it seems like a deliberate decision and changing it would likely confuse users. Unfortunately there is no way to scroll to the bottom of a full-column selection that starts from the first row or clicking the column header. I have a related request for .uno:GoToCell command: bug 123496
(In reply to Buovjaga from comment #2) > > So it seems like a deliberate decision and changing it would likely confuse > users. Not disputing your call but I haven't noticed any documentation defining the response so it's questionable as to which group of users gets confused - whichever way it goes ;).