Steps how to reproduce with Server Installation of "LibO 4.0.2.0+ - English UI / German Locale [Build ID: 01f8d0a1dffce854a66c0f957e81e6df6d361a8)]" {tinderbox: @6, pull time 2013-02-26 09:45:35} on German WIN7 Home Premium (64bit) with newly created user profile ….\LODev\4\: Under "Shortcut Keys for Spreadsheets" - "Navigating in Spreadsheets" you see Current Help ------------ Ctrl+Down Arrow: Moves the cursor to the bottom edge of the current data range. If the row below the cell that contains the cursor is empty, the cursor moves down to the next row that contains data. Problems -------- a) "current data range"? That can be confused with the "Data Range" Defined in Menu 'Data -> Define Range'. And where is defined that a data range is something with cells with contents? that's simpy wrong. b) bottom end of range? Cell cursor will be moved down in column! c) "If the row [...] is empty": That is wrong, it does not matter whetner there is some contents in an other column of the row, only cells in the column with the cell cursor in it count. d) what if cell cursor is around an empty cell? Correct Help: ------------ Ctrl+Down Arrow: Moves the cursor down in column to the last of adjacent cells with contents. If the cell below the cursor is empty, the cursor moves down to the next cell that contains data. If the cell with cursor is empty, cursor moves down in column to the first cell with contents. If the column below the cursor is empty the cursor will be moved down to last cell in the column. This also has to be corrected correspondent for all other Ctrl+Arrow help in that table
Confirmed: https://help.libreoffice.org/Calc/Shortcut_Keys_for_Spreadsheets#Navigating_in_Spreadsheets
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Olivier Hallot committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/+/c564fc53c7a5c1e2839876998edd13a4dfba03d1%5E%21 tdf#61586 Correct usage of Ctrl+Arrows in Calc