Created attachment 122744 [details]
broken conditional formatting
If a conditional format is specified for a column like "F:F" it is stored in Conditional Formatting as "F1:F1048576" rather than "F:F".
If the rows are then reordered using Alt+Drag, the Conditional Formatting breaks and is fragmented into multiple small pieces.
F:F means that it applies to the entire column; don't break it up when things are moved around.
Please what is your LibreOffice version and your OS, few time ago some work have been done about the behavior of A:A and 1:1 with some actions, on the other hand there is a request for enhancement to reunify CF condition ranges.
Cell ranges with the same Conditional Formatting should be consolidated to 1 range.
CONDITIONAL FORMATTING: Option for reunify ranges with same conditions
Build ID: 2b9802c1994aa0b7dc6079e128979269cf95bc78
Locale: en-US (en_US)
Windows 7 Pro 64-bit
I see now.
Entire column/row was implemented for 5.0, https://wiki.documentfoundation.org/ReleaseNotes/5.0#A:A_.2F_1:1_entire_column.2Frow_references
Maybe Eike can take a look.
We might be able to fix the fragmentation.
However I think it makes no sense to store F:F in that case. It is not a formula reference but a cell range in that case.
Eike might have some additional ideas about F:F vs F1:F1048576 for ScRangeList/ScRange based references.
Please fix the fragmentation.
How to duplicate:
1 check CF = OK, no 'split ranges' range is A2:A1048576
2 delete a row A1476
4 check CF, where there was one range there are two:
with exactly the same rules.
Actually the real fix is to not split in the first place.
If I wanted a split, I'd do it myself.
This has been a problem 'forever' and still exists in 22.214.171.124
W7Pro SP1 64bit
This is still a problem in 126.96.36.199 on Windows 7 64-bit. If you try to create a range like C:F in the Conditional Formatting, it accepts it, but then converts it to C1:F1048576, which is both conceptually wrong and difficult to read.
If you then cut and paste rows, or Alt-Drag them up or down to organize them, the Conditional Formatting is broken into separate rules, like one for C25:F1048576,C1:F20 and a different but identical rule for C21:F24.
If you Sort the rows to organize them, the brokenness doesn't happen.
"F:F" does not mean "column F from cell 1 to cell 1048576"; it means "the entire column F".
> However I think it makes no sense to store F:F in that case. It is not a formula reference but a cell range in that case.
"F:F" means "the entire column F". That the spreadsheet is actually implemented as a large but finite number of rows (65536 or 1048576) is a programmer's implementation detail, not something that should be exposed to users.
http://superuser.com/q/160435 Can you reference an entire column in OpenOffice Calc (like A:A in Excel)?
Created attachment 138002 [details]
This kind of fragmenting is an every day occurrence
Is there any chance of this ever being fixed? I have to manually edit the conditional formatting spans dozens of times per day for years because of this. It's very frustrating.
F:F means "the entire column F". It does not mean "Column F, rows 1 through 1048576". The former does not make sense to break up when rows are swapped. It always means "the entire column F" even if you move cells up or down within that column.
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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Yes of course it's still a problem, it happens every day.
Version: 188.8.131.52 (x64)
Build ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159
CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win;
Locale: en-US (en_US); UI-Language: en-US