Bug 1372630 - Recently used colors list does not populate in LibreOffice Impress
Summary: Recently used colors list does not populate in LibreOffice Impress
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: libreoffice
Version: 24
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-02 09:21 UTC by Marcin Steć
Modified: 2017-07-25 12:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-25 12:09:18 UTC


Attachments (Terms of Use)
Text color palette with empty last used colors list. (22.28 KB, image/jpeg)
2016-09-02 09:21 UTC, Marcin Steć
no flags Details

Description Marcin Steć 2016-09-02 09:21:02 UTC
Created attachment 1197082 [details]
Text color palette with empty last used colors list.

Description of problem:
When font color is changed, recently used color should appear on "Last used colors" list that is below color palette. (I'm not sure English title of this field, I use Polish, where it's named "Ostatnio używane" )

Version-Release number of selected component (if applicable):

libreoffice-impress-5.1.5.2-3.fc24.x86_64

How reproducible:
Create new presentation.
Type something.
Mark the text.
Click "Font Color" button. Pick the color. USed color does not appear on the last used colors list.

 

Steps to Reproduce:
1.Create new presentation.
2.Type something.
3.Click "Font Color" button. Pick the color.Text color should change.
4.Click the "Font color again" - Check "Last used" colors list.

Actual results:
Last used color list empty.

Expected results:
Changed color should be on the list. 

Additional info:

Comment 1 Caolan McNamara 2016-09-02 11:52:41 UTC
This must be if you click the button directly and don't click the dropdown and then select. I see the color indeed doesn't get set as recently used in this scenario.


Note You need to log in before you can comment on or make changes to this bug.