Steps how to reproduce with "LibreOffice 3.6.3.1” German UI/ German Locale [Build-ID: f8fce0b] on German WIN7 Home Premium (64bit) 1. Download / Open attachment 68921 [details] of Bug 56279 2. Activate Navigator, check comments You see "11", ""12", "13" 3. Select cells B5:C5 using Mouse 4. Menu 'Format -> Merge Cells -> Merge and Center Cells Bug: Comment "11" lost Problem is no longer visible with parallel installation of Master "LOdev 3.7.0.0.alpha0+ - ENGLISH UI / German Locale [Build ID: 370m0(Build:0)]" {tinderbox: @6, pull time 2012-10-20 14:21:35} on German WIN7 Home Premium (64bit) with separate User Profile for Master Branch Already [Reproducible] with Server Installation of "LibreOffice 3.5.1.2 German UI/Locale [Build-ID: dc9775d-05ecbee-0851ad3-1586698-727bf66] on German WIN7 Home Premium (64bit) Was ok with 3.3.3 @peter.weber@ims.co.at: Can you confirm this problem?
Problem is reproducible with LibreOffice 3.6.2.2 English on SuSE Linux 12.1 x86_64: 1. Using attachment 68921 [details] (sample201.ods): Contains comments in B5 ("11), E5 ("22") and I5 ("33"). 2. If I select cells A5:B5 using the mouse 3. Menu Format -> Merge Cells -> Merge and Center Cells ==> Comment "11" is lost
New Due to comment 1 @Peter Weber: Thank you for confirmation! @Spreadsheet Team Please set Status to ASSIGNED and add yourself to "Assigned To" if you accept this Bug or forward the Bug if it's not your turf (and remove others in team from CC).
*** Bug 88355 has been marked as a duplicate of this bug. ***
Still occurs in 4.3.4.1, 4.4rc and 4.5 master
** 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 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
Still repro with 5.4+ master.
Hi, Several cases can be encountered, when merging several cells, and requesting moving contents (and comments) to first cell: 1. There is only *one* commented cell in the area to be merged, and it is the *first* cell: comment is preserved and not modify. It already works like that. 2. There is only *one* commented cell in the area to be merged, but it is NOT the first cell: comment should be moved to the first cell, with its formats (text, area, line). It is what is requested in this bug report. 3. There are *several* commented cells in the area to be merged and the *first* cell has a comment: comments should be concatenated to first one, but formats will be lost (like for contents). 4. There are *several* commented cells in the area to be merged but the *first* cell do NOT have comment: first comment should be moved to first cell and other comments should be concatenated to first one, but formats will be lost (like for contents). How should comments be concatenated in 3. and 4.? I suggest to add a new line between comments, contrary to contents which are concatenated with blanks. In case 4., what is the first comment? For instance, when merging A1:B2, if there is no comment in A1, but comment in A2 and B1, which one is the first? I would suggest B1, but should it be language dependent?
An empty line between each concatenated comment seems fine. For #4, B1 seems fine. In other words, concatenate row-wise from lower columns to highre columns. This should not be language dependent (I assume you mean script dependent) as for languages written in RTL scripts the sheet area can be (and usually is) mirrored as well, with column A being the rightmost column. I suggest to refrain from any inspection of the comment content itself.
(In reply to Eike Rathke from comment #8) > An empty line between each concatenated comment seems fine. > For #4, B1 seems fine. In other words, concatenate row-wise from lower > columns to highre columns. This should not be language dependent (I assume > you mean script dependent) as for languages written in RTL scripts the sheet > area can be (and usually is) mirrored as well, with column A being the > rightmost column. > I suggest to refrain from any inspection of the comment content itself. Hi Eike, Could you have a look to my proposition https://gerrit.libreoffice.org/34162/ Many thanks in advance.
Dear developer, This bug has been in ASSIGNED status for more than 3 months without any activity. Resetting it to NEW. Please assigned it back to yourself if you're still working on this.
** 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+
Repro 7.5+