Description: When you merge cells (eg. A1, B1 and C1) and duplicate them in A2 the cells overlap each other. You have the merged cell which's content covers B2 and C2, but you can also select A2 and C2 on it's own and add content to them. Steps to Reproduce: 1. Select multiple cells (eg. A1, B1 and C1) and merge them 2. Select A2 and press Ctrl + D to duplicate the cell Actual Results: The existing merged cell is duplicated and overlaps B2 and C2, however you can also still select B2 and C2 and add data to them Expected Results: The merge cell (A1 to C1) is duplicated in A2 to C2 and covers the whole area of all three cells. B2 and C2 are not selectable with arrow key or with the mouse Reproducible: Always User Profile Reset: No Additional Info: Cell selection (with arrow keys, mouse works as well) in attached image: 1) Select merged cell A1-C1 2) press right once to get to D1 3) Select the duplicate of the merged cell at A2 4) press right once to get to B2 5) press right once to get to C2 Important NOTE for attached .ods file: Closing and reopening the file seems to clear the bug, so I guess the cell is saved correctly, but displayed wrong. To get the described bug just select A2 and press Ctrl + D. Version: 6.4.4.2 (x64) Build-ID: 3d775be2011f3886db32dfd395a6a6d1ca2630ff CPU-Threads: 6; BS: Windows 6.1 Service Pack 1 Build 7601; UI-Render: Standard; VCL: win; Gebietsschema: de-AT (de_AT); UI-Sprache: de-DE Calc: CL
Created attachment 162928 [details] bug in detail
Created attachment 162929 [details] ods file for bug
I confirm the behavior, what you describe is correct. what I don't know if this is a bug or not. Because E and F in my video are still there after unmerge... I didn't find a place with the description for the right behavior for Ctrl + D. Version: 6.4.5.2 Build ID: a726b36747cf2001e06b58ad5db1aa3a9a1872d6 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: ro-RO (ro_RO.UTF-8); UI-Language: en-US Calc: threaded
Created attachment 162931 [details] video with the bug I am not sure it's a bug, but if YES thiv video could be useful.
Dear BDF, 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
(In reply to QA Administrators from comment #5) > Dear BDF, > > [...] > > Warm Regards, > QA Team > Dear QA Administrators, Yes the bug still exists as described and can be reproduced without any big effort in LibreOffice calc Version: 7.3.4.2 / LibreOffice Community Build ID: 728fec16bd5f605073805c3c9e7c4212a0120dc5 CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: de-AT (de_AT.UTF-8); UI: de-DE Flatpak Calc: threaded Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.13.0-52-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 30.8 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: Micro-Star International Co., Ltd. Product Name: Bravo 17 A4DDR System Version: REV:1.0 Since the bug is over a year old I most certainly tried this on my Windows machine. I will add another comment when I tested it on Windows. Since the same bug exists on Linux, I expect the bug to still exist in Windows.