View Issue Details

IDProjectCategoryView StatusLast Update
0023550mantisbtcustomizationpublic2019-03-11 11:53
ReportercproensaAssigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Product Version2.8.0 
Target VersionFixed in Version 
Summary0023550: Modification to status colors css

The generated css for status colors has definitions for "color" and "background-color".
There are two issues:
1) Currently the status css is used for coloring fa-square icons, which only use the "color" attribute.
2) Having both color and background defined in the same rule is not useful, to be able to reuse this class, i would probably need either color, or background, but not both. For examle, this class as is would render a text in the same color as background.

bug_update_page uses this class to apply background coulour. Fortunately, the only content in the cell is an input that is not affected by those color styles.

The proposal is to have both:
status-xx-color: defining only "color" attribute
status-xx-background-color: defining only "background-color" attribute

And use them appropiately, and have it available to be used for customizations.

TagsNo tags attached.


has duplicate 0024534 closedatrol Bad generated CSS for status icon 




2017-10-26 07:14

developer   ~0058063

Do we need the background color?
We could also remove it and change bug_update_page to display the colored square.



2017-10-26 10:04

developer   ~0058068

We could also remove it and change bug_update_page to display the colored square.

Probably yes. However, with any method, there is some inconsistency when the field is editable and you select a different status, the color does not change.

We could also remove it and change bug_update_page to display the colored square.

In my case, i'd want to use those in customizations, eg: plugins, custom functions... Having those available is a great help.



2019-03-11 11:53

reporter   ~0061665

Having both color + background set equally together creates two issues.
The one reported in (duplicate) ticket 0024534
and when a status cannot be changed, there is no dropdown button, therefore the status cannot be read.

From my point of view on the UX, the color should be limited to the status square and nothing more.

Kind Regards

Issue History

Date Modified Username Field Change
2017-10-26 07:08 cproensa New Issue
2017-10-26 07:14 atrol Note Added: 0058063
2017-10-26 10:04 cproensa Note Added: 0058068
2018-06-11 11:36 atrol Relationship added has duplicate 0024534
2019-03-11 11:53 jeromedl Note Added: 0061665