Bug 135140 - Conditional formatting dialog prompt does not show existing condition when applying new formatting
Summary: Conditional formatting dialog prompt does not show existing condition when ap...
Status: RESOLVED DUPLICATE of bug 123927
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.0.0.0.beta1+
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks:
 
Reported: 2020-07-26 08:35 UTC by avirupkundu
Modified: 2020-07-27 21:38 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description avirupkundu 2020-07-26 08:35:43 UTC
Description:
If a cell has an existing Conditional Format, then trying to apply a new Conditional format causes a confirmation dialog to show with the following text:

"The selected cell already contains conditional formatting. You can either edit the existing conditional format or you define a new overlapping conditional format.

Do you want to edit the existing conditional format?"

However on selecting Yes, in the Conditional Formatting dialog box that opens, the existing condition is not available. 

Steps to Reproduce:
1.Select the entire sheet using the top left corner button.
2.Apply a conditional formatting
3.Save the file and exit.
4.Reopen the file
5.Apply Conditional->Condition Formatting on a single cell.
6.Select Yes from the Dialog.

Actual Results:
The Conditional Formatting Dialog does not contain existing condition.

Expected Results:
The conditional formatting dialog should contain the existing condition.


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.0.0.0.beta1 (x64)
Build ID: 94f789cbb33335b4a511c319542c7bdc31ff3b3c
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: en-IN (en_IN); UI: en-US
Calc: CL
Comment 1 raal 2020-07-27 21:22:07 UTC
I can confirm with Version: 7.1.0.0.alpha0+
Build ID: abea0d6647c7f1f7e76c73c26cb80e6a67dc5111
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded

Works in LO 4.2, regression
Comment 2 raal 2020-07-27 21:37:20 UTC
This seems to have begun at the below commit.
Adding Cc: to Markus Mohrhard; Could you possibly take a look at this one?
Thanks
 e95c186bc83eaea3cf81a731020ce36f7ed4b72b is the first bad commit
commit e95c186bc83eaea3cf81a731020ce36f7ed4b72b
Author: Jenkins Build User <tdf@pollux.tdf>
Date:   Fri Sep 30 08:21:44 2016 +0200

    source 5b8c22379e2eae74f7ed78326ab89483db5c6624

author	Markus Mohrhard <markus.mohrhard@googlemail.com>	2016-09-18 16:14:35 +0200
committer	Markus Mohrhard <markus.mohrhard@googlemail.com>	2016-09-19 10:10:09 +0000
commit 5b8c22379e2eae74f7ed78326ab89483db5c6624 (patch)
tree 60cbfdd24bca243b4a911ff1dab298ef91590b5b
parent 96646c351e20fa6699fa368457a05ee70f76f103 (diff)
tdf#96453, tdf#100793 rework transfer of data between cond format dlgs
Comment 3 raal 2020-07-27 21:38:58 UTC

*** This bug has been marked as a duplicate of bug 123927 ***