Bug 995051

Summary: Decision Table Wizard: mandatory fields labels unreadable
Product: [Retired] JBoss BRMS Platform 6 Reporter: Zuzana Krejčová <zkrejcov>
Component: Business CentralAssignee: manstis
Status: CLOSED CURRENTRELEASE QA Contact: Radovan Synek <rsynek>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: lpetrovi
Target Milestone: ER4   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 20:16:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
bad colour scheme none

Description Zuzana Krejčová 2013-08-08 13:13:03 UTC
Created attachment 784347 [details]
bad colour scheme

Description of problem:
When configuring a Decision Table through the Wizard, there are a few fields that are mandatory for certain columns, they are marked by a red asterisk. When these fields are not filled in properly, the label font colour is dark brown/grey and the background colour dark red. This combination makes the labels quite unreadable.
The brighter red asterisk on a darker red background also isn't a good choice.


Version-Release number of selected component (if applicable):
kie-wb 6.0 CR1

Comment 2 manstis 2013-09-06 21:34:08 UTC
Improved the contrast. If you have any better recommendations please suggest.

Comment 3 Zuzana Krejčová 2013-09-09 09:08:16 UTC
(In reply to manstis from comment #2)
> Improved the contrast. If you have any better recommendations please suggest.

This should definitely help. 
Though I do wonder, whether it would be possible and perhaps better to use the same background colour for all the warnings and invalid things. Or perhaps redesign the mandatory and valid/invalid fields' look and behaviour.
Right now though, getting it readable is enough, thanks.

Comment 4 manstis 2013-09-09 09:21:34 UTC
I agree. The problem we have is some (older) editors/widgets use vanilla GWT whereas newer ones use GWT-Bootstrap. The older ones should ideally all be refactored to use GWT-Bootstrap but this is a non-trivial task; and not something we'd have time for 6.0. 

Could you raise new BZs for where you see "old style" validation (an example of "new" would be the "New Repository" popup on the Administration perspective) and we can refactor in subsequent releases.

Comment 8 Radovan Synek 2013-10-18 07:46:21 UTC
Verified on BPMS-6.0.0.ER4