Bug #10392
closed
Compliance bar graph doesn't show small compliance numbers
Added by Jonathan CLARKE over 7 years ago.
Updated over 7 years ago.
Category:
Web - Compliance & node report
Severity:
Trivial - no functional impact | cosmetic
User visibility:
Getting started - demo | first install | level 1 Techniques
Description
This is from a 4.0.3 installation of Rudder, I don't know what other versions are affected:
![](/attachments/download/1192/1.png)
As you can see, "99%" is correctly displayed but the other two sections just say "<1", and something that is unreadable.
Files
1.png (9.71 KB)
1.png |
|
Jonathan CLARKE, 2017-03-10 11:38
|
|
This is on Chrome, by the way.
The fact that "<1%" is displayed in place of the actual number is by (your :) design choice, to let small number have a non-negligible part of the part (and so not be missed).
But clearly, we should be able to see the whole "<1%" text, be it with smaller font or broader zone for them (more likelly the second option).
François ARMAND wrote:
The fact that "<1%" is displayed in place of the actual number is by (your :) design choice, to let small number have a non-negligible part of the part (and so not be missed).
Yes, and that is great, but is not the subject of this bug (although it was not my design choice, but a request from several Rudder users)
But clearly, we should be able to see the whole "<1%" text, be it with smaller font or broader zone for them (more likelly the second option).
I think a smaller font would be fine. The fonts (and the graphs in fact) on this page are in general HUGE. Also, it's not overly surprising to have a smaller font for a smaller section - although that might not be visually pleasing. This is the case for "<1%", but I imagine it might well be the same for "2%" or even "3%", depending on the size of each section of the bar graph.
- Severity changed from Minor - inconvenience | misleading | easy workaround to Trivial - no functional impact | cosmetic
- Effort required set to Small
This may only happen on Chrome.
Working properly on my debian 8 firefox 51
- Target version set to 4.0.4
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/1616
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
- Priority changed from 40 to 39
This bug has been fixed in Rudder 4.0.4 and 4.1.1 which were released today.
Also available in: Atom
PDF