Description: I have customized toolbar with multiple "Background Color" commands. They default to yellow but I change them to an array of colors to keep my spreadsheets organized. Since the update, they will refresh every minute or so all back to the default yellow. Steps to Reproduce: 1. Change the color of a cell to something other than the default yellow. 2. Type anything into any cell. 3. Toolbar will reset the color selection back to default yellow. Actual Results: The "Background Color" button will change from the previously selected color back to default yellow. Expected Results: Every other version of Calc has kept the color selection chosen until the program is closed. Reproducible: Always User Profile Reset: Yes Additional Info: Nothing further to add.
Are you using the Single Toolbar UI? Does this happen with other UI? Go to menu 'View > User Interface' and take note of your current UI. Then change it to some other UI and test whether the reported behavior is happening in that other UI too. Then you can return to your preferred UI by using the same menu. Please report your results. Additionally, in LO please go to Help > About and use the icon in the Version Information window to copy the information. Please paste that info in your next comment.
(In reply to hegquist from comment #0) > I have customized toolbar with multiple "Background Color" commands. They > default to yellow but I change them to an array of colors to keep my > spreadsheets organized. This never meant to be a supported workflow, and worked by accident. See many of the duplicates of Bug 154270 that ask for syncing the color of all visible buttons of the same kind. It's also essential for fixing bugs like Bug 34804 to have a single last used color. There is a supported workflow for several predefined formatting sets, which is styles (cell styles in this case), and I don't think we should maintain a competing DF-based solution (and esp. one that works only for colors but not for other formatting attributes).
*** Bug 157904 has been marked as a duplicate of this bug. ***