Description: On latest update of LibreOffice "Automatic" font (a number in this case) colour on spreadsheet cell with light green (00ff00) background is white and hardly visible and cannot be changed using "format cells, font effects" dialogue box. One cell font (a number) colour was succesfully changed by setting to "black", but then unable to change other cells (containing numbers) using "format clone". Selecting multiple cells on which to perform the operation will only change a cell with text in, not numbers. Steps to Reproduce: 1.Select a cell with light background and text (which will be white) 2.Right click, Format cells, Font effects. Then select black from dropdown, O.K. 3.Having changed one cell, try clone formatting, or try selecting multiple cells and repeating 1 and 2 above. The font colour will not change if it is a number, but will if it is text Actual Results: The colour of the text (which was "Automatic) changed to black on the first cell on which it was performed. I then tried clone formatting of this cell to other relevant cells but it did not work. The "Format cells, Font effects dialgue shows the text in these relevant cells to be black after clone formatting, but they are not and they cannot be changed except by undoing the clone formatting. Alternatively try selecting multiple cells on which to perform the operation. Only cells with text in change, those with numbers in won't Expected Results: Font, including numbers not just text, to change to black so it is visible on the light green background Reproducible: Always User Profile Reset: No Additional Info: Version: 24.8.3.2 (X86_64) / LibreOffice Community Build ID: 48a6bac9e7e268aeb4c3483fcf825c94556d9f92 CPU threads: 4; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded
This problem is known and fixed for version 25.2. Please use bug 161766 for a request to apply the fix to 24.8 as well. [I don't know if the developer will do it, though.] *** This bug has been marked as a duplicate of bug 161766 ***