Created attachment 1165203 [details]
exclamation mark is not properly visible
Description of problem:
As you can see at screenshot exclamation mark at end of error message is not obvious. It seems that sentence continues and rest of it is hidden. Only if user zooms page user can see that it is exclamation mark.
Version-Release number of selected component (if applicable):
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36
Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0
Steps to Reproduce:
1. open cluster create wizard
2. cluster name leave empty and input journal size to 0
3. check end of error messages
It is not obvious that at end of error messages is exclamation mark and it seems like end of sentence is hidden.
Exclamation marks are obvious.
Created attachment 1165206 [details]
exclamation mark is properly visible after zoom
Although the exclamation mark is not visible completely (which is the actual bug), from a UX perspective, we would suggest removing exclamation marks from all error/warning messages.
As a best practice, the error/warning message should:
(1) Avoid using exclamation marks in the message as this could be perceived as "scolding" the user.
(2) You probably don't need to use camel case in the message, e.g. Journal Size can be written as Journal size in the message.
(3) Error/warning messages should be helpful, e.g.
Invalid journal size. Specify a journal size value between 2 and 1024.
Related to https://bugzilla.redhat.com/show_bug.cgi?id=1343097.
Suggested priority is low and can be addressed after feature freeze.
Agreed with Ju here, in favor of removing the exclamation mark.
However, we should be careful selecting typefaces, cause in some scenario an exclamation mark is completely viable and this bug will crop up no matter what.
Under review: https://review.gerrithub.io/#/c/280398/
Fixed on the upstream: https://review.gerrithub.io/#/c/280398/
Moving to ON_QA
and it works.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.