Download it now!
Bug 107401 - On first sheet cells with copied conditional formatting are displayed not correctly formatted
Summary: On first sheet cells with copied conditional formatting are displayed not cor...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.4.0.0.alpha0+
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Conditional-Formatting
  Show dependency treegraph
 
Reported: 2017-04-24 21:04 UTC by Stefan_Lange_KA@T-Online.de
Modified: 2018-07-16 06:34 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
zip-File with 2 spreadsheets and 2 screenshots to reproduce resp. demonstrate the error (110.61 KB, application/x-zip-compressed)
2017-04-24 21:09 UTC, Stefan_Lange_KA@T-Online.de
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan_Lange_KA@T-Online.de 2017-04-24 21:04:43 UTC
Description:
IMHO the problem of Bug_106242 ist not completely resolved by the patch committed by Markus Mohrhard.
As I have written in comments #9, 10 and 12 with my test results to Bug_106242 there is still a problem.
It seems that no one has paid attention to the comments. Therefore I report the problem now as a new bug.

Subject of the problem: Copy + paste of 1RxNC ranges on the first sheet of a spreadsheet document
On the first sheet of a spreadsheet document all cells with copied conditional formatting are not displayed according to the correctly copied (!) conditional formatting immediatly after copy + paste - except the cells in the first column. Only after save, close and reopen the cells are correctly displayed.

Actual test was med with 
Version: 5.4.0.0.alpha0+ (x64)
Build-ID: 9223d88542a5b9272f98f37feb84cd78beacac42
CPU-Threads: 2; BS-Version: Windows 6.19; UI-Render: Standard; 
TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2017-04-24_15:05:46
Gebietsschema: de-DE (de_DE); Calc: group

Steps to Reproduce:
To demonstrate and reproduce the problem I have modified the spreadsheet file "Test_Cond_Format.ods" that I have attached on 27.03.2017 to Bug_106242.
The spreadsheet now consist of 2 identical sheets. When one makes the same copy and paste operations on both sheets the results are different. Only after save, close and reopen the first sheet is identical to the second sheet. See the attached screenshots and spredsheet documents! 

Copy + Paste operations on both sheets:
- complete row 5 copied to row 16 (source cells in one row: subject of the problem): On the first sheet (Tabelle1) only the cell in row A is displayed correctly formatted, other cells are displayed without the conditional formatting. On sheet Tabelle2 all copied cells are displayed correctly formatted. 
- rows 3 to 5 copied to rows 11 to 13 (cells of more than one row: not subject of the problem): On both sheets all copied cells are displayed correctly formatted.


Actual Results:  
see Steps to Reproduce

Expected Results:
see Steps to Reproduce


Reproducible: Always

User Profile Reset: No

Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0
Comment 1 Stefan_Lange_KA@T-Online.de 2017-04-24 21:09:59 UTC
Created attachment 132806 [details]
zip-File with 2 spreadsheets and 2 screenshots to reproduce resp. demonstrate the error
Comment 2 m.a.riosv 2017-04-24 22:50:13 UTC
There is a duplicate CF range for E1:E7 on the first sheet, but deleting the first of those, and doing the copy from row 6 to row 16, for E16 no red background, but without save, editing the CF for E16 without change nothing, Ok Ok, red backgroun appears.
Comment 3 QA Administrators 2018-07-16 02:41:56 UTC Comment hidden (obsolete)
Comment 4 Stefan_Lange_KA@T-Online.de 2018-07-16 06:34:31 UTC
I have tested with
 
Version: 6.0.5.2 (x64)
Build-ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16
CPU-Threads: 4; BS: Windows 10.0; UI-Render: GL; 
Gebietsschema: de-DE (de_DE); Calc: CL

Result: The problem exists no longer.

Additional information: In LO 6.0.0 the bug was still present, but I have not checked, in what version the problem really disappeared.