Description: End key moves a cursor not to the last cell with data in the row but moves to next cell if last cell is in merged cell range Steps to Reproduce: 1. Create a Calc spreadsheet 2. Select A1:D6 range 3. Set up all borders for the range (use drop-down widget on the toolbar) 4. Select A4 cell 5. Press End key => cursor moves to D4 cell, it's OK 6. Select C4:D4 cell range and merge cells using an icon on the toolbar 7. Select A4 cell 8. Press End key => cursor moves to E4 cell, it's an unexpected behavior. I would expected the cursor will should be on merged C4:D4 cell. Actual Results: End key moves a cursor not to the last cell with data in the row but moves to next cell if last cell is in merged cell range Expected Results: End key moves a cursor to the last cell with data in the row anyway Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: 52a49f9e480ca03e231cfda82640a928393131c9 CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: threaded and I checked in 6.1 too
Attila, I CC'ed you, because you are a guru in merged cells. What do you think about current behavior in this bug?
I've reproduced it in Version: 7.2.0.0.alpha0+ (x64) Build ID: ecb916667b633f8647790e040226b093760e6cfe CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
Dear Roman Kuznetsov, 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
Still repro in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b4dc43b6d01d85802d5674c3a27789d6354e39a8 CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL threaded