Description: Background color (set with relative value) isn't proper displayed when saving as OpenDocument (.ods) but it works as expected in Office Open XML (.xlsx) file. Steps to Reproduce: 1. Insert a random Numeric value (e.g. 100) in a random cell (e.g. A1) 2. Select a second random cell (e.g. B1) and go Format > Conditional > Color Scale... 3. Set Color Scale (2 Entries). Minimum (Value) 0, Maximum (Formula) as follow: =INDIRECT(ADDRESS(ROW(),COLUMN()-1)) 4. Insert a Numeric value from 0 to 100 in second cell (B1). 5. Create (save as) two separate files: one as .ods and another one as .xlsx 6. Close LibreOffice Calc and then re-open each file. Actual Results: Background cell (B1) is going to change from first picked color to second one in .xlsx. Same background cell (B1) will be blank in .ods file (only works again if you re-open Conditional Formating window, but if you close and re-open LibreOffice, background cell color is going to be blank again) Expected Results: .ods should work as .xlsx does Reproducible: Always User Profile Reset: Yes Additional Info: .xlsx works perfect. .ods doesn't works.
Please attach the xlsx sample file for test.
Created attachment 175855 [details] Three examples of Color Scale
Comment on attachment 175855 [details] Three examples of Color Scale This Office Open XML (.xlsx) file... ... is correctly displayed under LibreOffice Calc. ... is correctly displayed under G**gle Sheets. but, if you export it as OpenDocument (.ods) file... ... is NOT correctly displayed under LibreOffice Calc (cells are blank). ... is correctly displayed under G**gle Sheets.
[Automated Action] NeedInfo-To-Unconfirmed
I have changed the status to NEW. The bug is reproducible in: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: c8e3a9651e74ed25847ce5fbd335e07fdef87799 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: en-IN (en_IN); UI: en-US Calc: threaded
*** Bug 145465 has been marked as a duplicate of this bug. ***
Dear tftp9odf, 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