Description: Content gets pasted in two table cells when one cell is selected Steps to Reproduce: 1. Open attached file 2. Select 'AA' and copy it 3. Select 'BB' from left to right until cell B1 is completely selected 4. Press CTRL+V Actual Results: AA will be pasted into cell A1 and B1 Expected Results: The text should only be pasted into B1 Reproducible: Always User Profile Reset: No Additional Info: Found in Version: 5.4.0.0.alpha0+ Build ID: 79497f458727a0dea983847fe9d3873bf9c2e972 CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-01-24_03:10:09 Locale: nl-NL (nl_NL); Calc: CL and in Versie: 4.2.0.4 Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba71 but not in Versie: 4.1.0.4 Build ID: 89ea49ddacd9aa532507cbf852f2bb22b1ace28 User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Created attachment 130672 [details] Example file
Created attachment 130673 [details] Example file Variation 1. Open example file 2. Select the cell containing AA (not just AA) 3. Select the cell containing CC and paste AA (CTRL+V)
I can't reproduce it in Version: 5.4.0.0.alpha0+ Build ID: d3ff66999d924e832f8219c65ced0526f1a67f82 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group
Created attachment 130674 [details] Screencast
Repro with steps from desc. Arch Linux 64-bit, KDE Plasma 5 Version: 5.4.0.0.alpha0+ Build ID: 63fd4c97118a943c84ba5a666cf8c9cc54b511c7 CPU Threads: 8; OS Version: Linux 4.8; UI Render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on January 22th 2016
Reproduced even with 3.3.0 / Ubuntu 16.04, using the 1st example file with the steps shown in the screencast. => not a regression
@Aron. I think I found the cause for the different conclusions. Probably you created the test document yourself (and used a different order) If I exactly follow the steps (using the test document), I can't reproduce it (with Windows). I tested: Versie: 4.1.0.4 Build ID: 89ea49ddacd9aa532507cbf852f2bb22b1ace28 Versie 4.0.0.3 (Bouw-id: 7545bee9c2a0782548772a21bc84a9dcc583b89) and LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 However with a very small alteration I do reproduce your results into LibO3.3.0: 1. Open attachment 130672 [details] 2. Copy 'AA' 3. Click in the cell containing CC and make a change (add 'q' for example) 4. Select the complete cell; and paste (CTRL+V)
(In reply to Telesto from comment #7) > @Aron. > I think I found the cause for the different conclusions. Probably you > created the test document yourself (and used a different order) Nope, as I mentioned I used the first example (attachment 130672 [details]), and the screencast. And just now I reproduced it again with 3.3.0 / Windows 7. However, it only seems to come up starting from the second try after an undo, and not right away. Also note that I selected the cell with BB from right to left, then also the empty one, and moved back into BB's territory before letting the mouse button go and hitting paste (this conforms your screencast, but not the initial description).
** 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 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 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Repro 6.3+ per comment 8 that follows screencast. Steps are not correct.
Dear Telesto, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Seems duplicate of the same reporter known for own duplicates. *** This bug has been marked as a duplicate of bug 119540 ***