https://bugs.documentfoundation.org/show_bug.cgi?id=174084

            Bug ID: 174084
           Summary: Conditional formatting custom style name is ignored
                    and default name is saved instead
           Product: LibreOffice
           Version: 26.8.0.3 release
          Hardware: x86-64 (AMD64)
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Calc
          Assignee: [email protected]
          Reporter: [email protected]

Description:
Hello. I've found a bug in Calc in conditional formatting editor.

Creating new style from inside the conditional formatting conditions editor
window, that style gets a default name of "Untitled1". If at that point user
changes that style name, eg. to "My Custom Style", and confirms adding that
style, then in the "Apply style" for that condition the style "Untitled1" is
set instead of "My Custom Style". Additionally, in "Apply style" dropdown list,
"My Custom Style" is nowhere to be seen.
Once saved, naturally, the condition does not work.

User has to then re-open that condition for editting. At that point the "Apply
style" value is set to blank. Now, however, "My Custom Style" is present in the
drop down list to choose, after which and saving the condition start working.

Attached a screen capture showing exactly that.


Steps to Reproduce:
1. Open conditional formatting.
2. Add condition.
3. In "Apply style" choose "New style..."
4. Change default style name of "Untitled1" to a custom one eg. "My Custom
Style".
5. Save "My Custom Style".


Actual Results:
"My Custom Style" isn't saved as "Apply style" value for the condition, instead
a default and non-existent "Untitled1" style name is stored there.

Expected Results:
"Apply style" value should be set to "My Custom Style", NOT to non-existent
"Untitled1" style.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
It should work as expected ;)

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to