Created attachment 83657 [details] Spreadsheet with conditional formatting (alternate colours) I set up conditional formatting in Calc such that different background colours appear on alternate rows. If new rows are inserted directly below the rows where the conditional formatting is applied, the new rows correctly display the alternate background colours. However, when the spreadsheet document is saved, closed and then reopened, the new rows lose the alternate background colours (i.e. the conditional formatting is lost). See the attached file. It should be noted that this problem was not inherited from OpenOffice. If the attached file is opened in OpenOffice and new rows are inserted in the same way (i.e. directly below the conditional formatting range), the alternate colours applied to the new rows are preserved after document reopening.
This is a problem of the new conditional format storage. I'll see what I can do to fix it.
Markus Mohrhard committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=5d9e062a68eaf7544d02501d7b221150d74f7555 increase conditional format range during inserting rows/cols, fdo#67783 The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Markus Mohrhard committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=fd2f96c2ff83bee968fec8aa7c402ae02e78e2e4 add test case for fdo#67783 The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
I assume this is fixed and the bug's status was not set accordingly. Doing so. If this was wrong then please reopen with a comment.
I have tested with version 4.1.3.2 and the bug still occurs
(In reply to comment #5) > I have tested with version 4.1.3.2 and the bug still occurs This is only fixed in 4.2.0 Please check the whiteboard line before you reopen bug reports.
Apologies..thanks for fixing the bug