Issue 60656 - color buttons in text object bar should all behave the same way
Summary: color buttons in text object bar should all behave the same way
Alias: None
Product: Writer
Classification: Application
Component: editing (show other issues)
Version: 680m150
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
: 60657 (view as issue list)
Depends on:
Reported: 2006-01-16 19:27 UTC by robertpopa22
Modified: 2013-02-07 22:36 UTC (History)
1 user (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description robertpopa22 2006-01-16 19:27:07 UTC
The Background color button should be made of 2 separate buttons simillar to the
Foreground button
Comment 1 robertpopa22 2006-01-16 19:32:17 UTC
The buttons from the toolbar
Comment 2 hwoarang 2006-01-16 23:46:40 UTC
*** Issue 60657 has been marked as a duplicate of this issue. ***
Comment 3 michael.ruess 2006-01-17 10:54:19 UTC
I do not understand what you desire here... there is aone button for Font color,
one for character background color and one for paragraph beckground color.
so what do you mean by "should be made of 2 separate buttons"?
Comment 4 robertpopa22 2006-01-18 10:09:47 UTC
Our suggestion to have the SAME BEHAVIOR for all the elements that are simillar. 
So regarding Backgound Color, Highlight and Foreground color there is no similar
behavior between them. The Foreground is the only button that works as expected
(like in ms office, corel or other suites). It has 2 separate parts:
- a colour picker (the down arrow) which changes the selected colour 
- and the actual foreground button that applies the colour on the text and also
remembers the colour. 
Theese buttons should be acting exactly the same in all the suite... I hope its
clear now :)
Comment 5 robertpopa22 2006-01-18 10:19:01 UTC
A little corection:
Also the highlight button is ok! It remains for the background button to be

Comment 6 michael.ruess 2006-01-18 11:31:14 UTC
Reassigned to requirements.
Comment 7 robertpopa22 2009-05-12 19:40:53 UTC
This issue also remained unresolved in release 3.1