Bug 72991 - Font, highlight and background color in toolbar buttons is not remembered for next session
Summary: Font, highlight and background color in toolbar buttons is not remembered for...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 96564 (view as bug list)
Depends on: 113433
Blocks: 34804 Split-Group-Buttons-Color
  Show dependency treegraph
 
Reported: 2013-12-23 17:38 UTC by David Jakubec
Modified: 2018-05-29 19:56 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
small picture (10.08 KB, image/jpeg)
2013-12-23 17:38 UTC, David Jakubec
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Jakubec 2013-12-23 17:38:21 UTC
Created attachment 91158 [details]
small picture

Don't keep selected buttons colors in versions 4.3.2 and 4.2.0.1
Comment 1 Stanislav Horacek 2013-12-24 13:59:12 UTC
I can confirm this for 4.2.0.1, Ubuntu 13.10.

Steps to reproduce:
1. Open Writer.
2. In Formatting toolbar, click on the dropdown for Font color icon and select an arbitrary color.
3. Close Writer and open it again.
4. Font icon color is reset to the default one, it is not the color you selected.

Expected: Font icon color should be the selected one.

The same applies to highlighting and background icons. This probably never worked, reproducible also in 3.5.
Comment 2 Maxim Monastirsky 2014-02-02 16:27:27 UTC
feature request
Comment 3 Maxim Monastirsky 2015-12-20 19:29:11 UTC
*** Bug 96564 has been marked as a duplicate of this bug. ***
Comment 4 Maxim Monastirsky 2017-10-24 08:35:18 UTC
*** Bug 83789 has been marked as a duplicate of this bug. ***
Comment 5 Maxim Monastirsky 2017-10-24 09:02:30 UTC
*** Bug 71413 has been marked as a duplicate of this bug. ***
Comment 6 Maxim Monastirsky 2017-10-30 07:20:31 UTC
*** Bug 113433 has been marked as a duplicate of this bug. ***