Download it now!
Bug 101285 - Manage Conditional Formatting dialog doesn't remember position, column sizes, and range selection
Summary: Manage Conditional Formatting dialog doesn't remember position, column sizes,...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) rc
Hardware: All All
: medium minor
Assignee: Not Assigned
Depends on:
Blocks: Dialog Conditional-Formatting-Managing
  Show dependency treegraph
Reported: 2016-08-04 04:07 UTC by Dan Dascalescu
Modified: 2020-03-08 02:50 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Conditional Formatting Manage dialog with long ranges (109.67 KB, image/png)
2016-08-04 04:07 UTC, Dan Dascalescu

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Dascalescu 2016-08-04 04:07:30 UTC
Created attachment 126566 [details]
Conditional Formatting Manage dialog with long ranges

1. In a spreadsheet with conditional formats, open Format -> Conditional Formatting -> Manage
2. Move the dialog (you might want to see some calls behind it in the spreadsheet)
3. Resize the Range column (some ranges can contain many cells)
4. Click on a range other than the first
5. Click Edit...
6. In the newly opened dialog, click Cancel

Notice that,
1. The position of the Manage dialog was reset so that it's in the middle of the parent LibreCalc window
2. The column widths have been reset as well, and you can no longer see the full range.
3. The first range is selected, instead of the one you edited.

This is annoying because as seen in the screenshot, I have a number of single-cell ranges which I suspect have the same conditions, but it's hard to go over each of them and verify that (which range I selected is reset when I close the Edit... dialog, and the first range is selected instead).
Comment 1 Buovjaga 2016-08-07 15:26:08 UTC

Arch Linux 64-bit, KDE Plasma 5
Build ID: f3d26af51588af441f62fb69bb7a5432845226ac
CPU Threads: 8; OS Version: Linux 4.6; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on August 5th 2016
Comment 2 QA Administrators 2018-01-16 03:29:32 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2020-03-08 02:50:44 UTC
Dear Dan Dascalescu,

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

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

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:

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team