Description of problem: In Edit mode, user can enter any number of appropriate colors in the "Background" field, hit tab, and the color is changed. However if user enters something invalid, it is accepted (and messages indicate that it is saved). Version-Release number of selected component (if applicable): How reproducible: Every time. Steps to Reproduce: 1. Go into edit mode for a dashboard tab. 2. in the free text field, enter the value "red" and hit tab. Notice the color change and the message tray notice that it was successfully saved 3. Repeat step 2 with valid hex or named colors, i.e., "limegreen", "slategray", "skyblue" 4. Repeat again with the term "snortblatt" Actual results: Value gets saved regardless as to whether it is bogus. Expected results: Rejection? Additional info: Interestingly, navigating away from dash and back to it, the color of the dash itself is returned to something sane, white. The bogus value remains in the field however.
Also another interesting aside, multibyte chars entered into that field _do_ get rejected -- the value gets reverted back to the last known good value.
commit 4c20f81 using new rhq color button item component. it uses less real estate than the original color picker item and it avoids allowing you to enter invalid colors. to see this - go to edit the dashboard and see there is a new "Background" button. click it and you can select a color.
Verified.
Bookkeeping - closing bug - fixed in recent release.