In Writer, when you have a table and you want to select the entire table using the arrow in the top left corner (when you place the mouse right outside the table in the top-left corner), the cursor moves to the last cell in the table, at the bottom-right end. The expected behavior is that the cursor will remain in the first cell (in the top-left corner). Reasons for this change: 1) The current behavior is bad for tables that are longer than the current view... so when you select the entire table, the view moves to the end of the table, which is very disruptive. 2) Moreover, the current implementation is not consistent with the behavior we have when you select an entire row or column. In these cases, the cursor stays in the first row or column (which is the expected behavior). Therefore, when you select the entire table, the cursor should be positioned in the first table cell.
I can't confirm it with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 69d0be09ad81935f7da4b6f8d036c3562357d068 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (de_DE); UI: en-GB Calc: CL threaded Actual result: If arrow appears and you select all rows from a position outsie the table, position of cursor doesn't change. But if you select cells just within the table, cursor position changes.
Confirm with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 8cd29dac4046e38bcf14784accab94ad1b4ac4d7 CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded and Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Dear Rafael Lima, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://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: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug