Created attachment 125015 [details] Screenshot of the error in calc I connected 4 times 6 cells vertically and added a conditional formatting over these connected cells that adjusts the background color of the cells depending on their value. In Libreoffice Calc, only the background of the first original cell is adjusted (see screenshot). If I export an xlsx in Calc and open the file in Microsoft Excel, Excel adjusts the background color of the complete cell, not only the first.
Created attachment 125016 [details] Test At Step 9 Summary: I can confirm this on Version: 5.1.3.2 in Windows 10, but with some stipulations. When applying a background as conditional formatting to a block of merged cells, only the first "original" cell will get the background applied. However, If you double click the cell and then click and other cell, the formatting will be applied to the entire merged block. Though, this may be exclusive to my version of LibreOffice, so I do not know If this "fix" works for earlier versions. Steps: 1. Open a new LibreOffice Calc spreadsheet. 2. Highlight cells A1-A5 and right click on the cells. (I used cells D1-D5, but it doesn't really matter) 3. Click Merge cells 4. Click the new block of merged cells and type 0 in it. 5. From the Menu, click Format>Conditional Formatting>Condition... 6. Click add to add a new condition 7. In this new Condition, set the condition to "Cell value is" "Equal to" "0" 8. From the drop down menu next to Apply Style, click New Style. Click the background tab, choose any non-white color, and click OK. 9. Click OK to close the conditional formatting window. Expected Result: The entire merged cell's background color is what you selected in the conditional formatting Actual Result: Only the first "original cell" in the merged block has the formatting applied to it. After Step 9, you can quickly fix the issue by the following steps: 10. Double click the merged cell. It should turn white and the text input cursor should appear in it. 11. Click on any cell outside of the merged cell block. the background color should now be applied to the entire merged block.
Created attachment 125017 [details] test after step 11
Created attachment 125020 [details] merged cells color bars
I can confirm your workaround on this simple example. But it does not work with a color bar (is this the right english term? gradient?). 1. Open a new LibreOffice Calc spreadsheet. 2. Enter 1 in A1, 2 in B1 3. Highlight cells A1-A2 and right click on the cells and click merge cells 4. Highlight cells b1-B2 and right click on the cells and click merge cells 5. Highlight the two merged cells 6. From the Menu, click Format>Conditional Formatting>Color bars 7. Keep the default and click ok to close the conditional formatting window. Expected Result: The two merged cell's should be entirely have a background color Actual Result: Only the first "original cell" in the merged blocks has the formatting applied to it. 10. Double click one of the merged cells. It should turn white and the text input cursor should appear in it. 11. Click on any cell outside of the merged cell block. Result: No change, still only the first "original cell" has a different background color. Screenshot just added.
Upon further testing, it seems that if a merged cell has "color scale" condition formatting applied to it and then removed, a subsequent "conditional" condition formatting work as intended. Steps: 1. Open a new LibreOffice Calc spreadsheet. 2. Enter 1 in A1, 2 in B1 3. Highlight cells A1-A2 and right click on the cells and click merge cells 4. Highlight cells b1-B2 and right click on the cells and click merge cells 5. Highlight the two merged cells 6. From the Menu, click Format>Conditional Formatting>Color Scale 7. Keep the default and click ok to close the conditional formatting window. 8. From the Menu, click Format>Conditional Formatting>Manage. Select the newly made entry and click remove, then ok 9. From the Menu, click Format>Conditional Formatting>Condition... 10. Click add. In the new window, set the condition to "Cell value is" "Not equal to" "0" 11. From the drop down menu next to Apply Style, click New Style. Click the background tab, choose any non-white color, and click OK. 12. Click OK to close the conditional formatting window.
** 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
This bug still remains, I just encountered it in a fresh install of the most recent version, more specifically: Version: 6.0.1.1 (x64) Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: en-GB (en_GB); Calc: CL
This bug persist. Test sheet is uploaded to https://www.dropbox.com/s/d275kt8manqncsa/2018-07-27%201526%20colour%20formatting%20in%20merged%20cells.ods?dl=0 View in LO 6.0.5.2 (x64) https://www.dropbox.com/s/6xb08m6lm131jjy/2018-07-27%201526%20colour%20formatting%20in%20merged%20cells.png?dl=0
Dear libreoffice, 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
Just tried with the following LibreOffice version and this bug is still there: Version: 6.2.5.2 (x64) Build-ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159 CPU-Threads: 4; BS: Windows 6.1; UI-Render: Standard; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: threaded
This bug still persistin Version: 6.4.1.2 (x64) Build ID: 4d224e95b98b138af42a64d84056446d09082932 CPU threads: 8; OS: Windows 10.0 Build 18362; UI render: default; VCL: win; Locale: cs-CZ (cs_CZ); UI-Language: en-US Calc: threaded
The bug is still present in Version: 7.1.0.0.alpha0+ (x64) Build ID: 7dc3a20cab712ee987ea25a8f5728529521485b7 CPU threads: 8; OS: Windows 10.0 Build 18362; UI render: Skia/Raster; VCL: win Locale: cs-CZ (cs_CZ); UI: en-US Calc: CL
Dear libreoffice, 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
Note: it seems, no problem on Linux.
Tibor Nagy committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/e384be0f6ea6453e57cd4a7c4402d26b49debc41 tdf#99808 sc: fix background of conditional formatting in merged cell It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Tibor Nagy committed a patch related to this issue. It has been pushed to "libreoffice-7-6": https://git.libreoffice.org/core/commit/77720a8f4338f2b6e393387e6fb683339618e826 tdf#99808 sc: fix background of conditional formatting in merged cell It will be available in 7.6.0.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.