action #42017
closedon adding new test scenario in job templates the priority field looks disabled but is not
0%
Description
see attached screenshot, the "prio" up-down-field looks disabled (greyed out) but is not when adding a new test scenario to staging.
Files
Updated by coolo over 5 years ago
the text input is not disabled, but the value is - it's just showing the default value.
@hellcp, have a suggestion for us?
Updated by hellcp over 5 years ago
In cases when there is just one value, which you can't choose, just text is enough, if I understand this correctly.
Updated by coolo over 5 years ago
Sorry, a little background:
On adding a new job template we store NULL as priority, but show the default priority in the UI. Because once you enter something in that text field, this will overwrite the default. So this disabled looking text field is both to show the default and to enter a new one.
Updated by hellcp over 5 years ago
I don't see why it would need to be disabled then, it works like any value selection should :D
Updated by coolo over 5 years ago
It's not disabled - it just looks disabled as we wanted to make the difference between default value and real value clear. That's what this bug is all about :)
Updated by okurz over 5 years ago
coolo wrote:
make the difference between default value and real value clear.
Hm, true. It tricks the eyes thinking the background would be darker if the value is grey and not black but actually the background within the value box is the same in the case of default or overwritten. Well, how about italic text for default?
Updated by mkittler over 5 years ago
- Status changed from New to In Progress
- Assignee set to mkittler
It looks disabled indeed. Here's a PR to use italic font style instead: https://github.com/os-autoinst/openQA/pull/1818