Bug 122096 - FILEOPEN XLSX Conditional formatting with cell contains condition is imported with quotation marks
Summary: FILEOPEN XLSX Conditional formatting with cell contains condition is imported...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected)
4.1 all versions
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: filter:xlsx
Depends on:
Blocks: XLSX-Conditional-Formatting
  Show dependency treegraph
Reported: 2018-12-14 11:51 UTC by NISZ LibreOffice Team
Modified: 2022-12-19 03:18 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:
Regression By:

The original document. (17.13 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2018-12-14 11:52 UTC, NISZ LibreOffice Team
Screenshot of the original document side by side in Excel and Calc. (411.01 KB, image/png)
2018-12-14 11:52 UTC, NISZ LibreOffice Team
The example file in Excel 13 and LO7.2 nightly (107.54 KB, image/png)
2020-12-18 08:46 UTC, NISZ LibreOffice Team

Note You need to log in before you can comment on or make changes to this bug.
Description NISZ LibreOffice Team 2018-12-14 11:51:31 UTC
When you make a conditional formatting with cell contains a number with a “,” symbol (eg.: 1,23) it doesn’t work when opened in LO.

Steps to Reproduce:
    1. Create a new xlsx in LO.
    2. Create a new rule in conditional formatting.
    3. Set its condition to contains given text and set the text to 1,23
    4. Write some numbers to the area some of which contain the number and notice that the formatting works.
    5. Save the file and open it in LO.
    6. Notice the differences then write into one of the are this: “1,23” with the “ symbols.

Actual Results:
In LO the formatting only works when “1,23” is in the cell.

Expected Results:
It should work as it does in MSO so with both 1,23 and “1,23”.

Reproducible: Always

User Profile Reset: No

Additional Info:
Comment 1 NISZ LibreOffice Team 2018-12-14 11:52:22 UTC
Created attachment 147527 [details]
The original document.
Comment 2 NISZ LibreOffice Team 2018-12-14 11:52:42 UTC
Created attachment 147528 [details]
Screenshot of the original document side by side in Excel and Calc.
Comment 3 Roman Kuznetsov 2018-12-15 08:04:12 UTC
confirm in

Build ID: 3c964980da07892a02d5ac721d80558c459532d0
CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2018-12-12_02:07:45
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: threaded

in Excel condition is "Text contains 1,23". Do you see? TEXT. There isn't the same condition in Calc
Comment 4 Xisco Faulí 2018-12-18 13:50:40 UTC
Also reproduced in

Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53
Threads 4; Ver: 4.15; Render: default; 


Version (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Comment 5 QA Administrators 2020-12-18 03:50:58 UTC Comment hidden (obsolete)
Comment 6 NISZ LibreOffice Team 2020-12-18 08:46:19 UTC
Created attachment 168281 [details]
The example file in Excel 13 and LO7.2 nightly

Still a problem in:

Version: (x64)
Build ID: e97a81e94511b52987a50b7bdb72c922899da588
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: hu-HU (hu_HU); UI: en-US
Calc: CL

To clarify this example file was made in Excel 2010.
Comment 7 NISZ LibreOffice Team 2020-12-18 08:53:38 UTC
@Tibor maybe one more for you? This imports the condition as "1,23" but it really should just use 1,23 to get the same effect (for the number type cells at least).
Comment 8 QA Administrators 2022-12-19 03:18:24 UTC
Dear NISZ LibreOffice Team,

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