-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Description
This issue respects the following points:
- This issue is not already reported on GitHub (I've searched it).
- I agree to follow Jellyfin's Code of Conduct.
- This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.
Describe the bug
In the admin "Dashboard", directly under the "Scan All Libraries" button, the two media counts in each of the boxes for "Series Episodes" and "Albums Songs" lose any spacing between the two numbers and visually merge together appearing as one number at a certain width when those numbers are large enough. With larger widths they are separated by enough space to distinguish the numbers and with narrower widths the grid is responsive, rearranges the layout, and again the counts are separated by enough space. So this happens only when:
- the counts are large, I see it when the total number of digits between the two counts is 8-9 digits
- only a very specifc, small range of widths just before the grid system responds and rearranges
Reproduction Steps
Testing in Chrome, as I increase and decrease the width using the browser's zoom, first 9 digit combined counts then 8 digit combined counts merge, then the grid responds, rearranges the layout, and restores the spacing. This happens when the counts grid changes from 3 to 2 columns as well as when the outer grid system places the "Activity" and "Paths" boxes to the right then below.
Expected/Actual behaviour
The responsive UI should maintain visual separation even when the counts are large, even if it has to elide (...) those counts. Personally, I'd prefer the counts be changed to use magnitude suffixes when the numbers are large enough: 1,001 10,001 -> 1k 10k .
Server version
10.11.3
Web version
10.11.3
Build version
10.11.3
Platform
Linux Docker: image: "ghcr.io/jellyfin/jellyfin"
Browser
Chrome v144.0.7534.0
Additional information
Very minor, I would prioritize this below pretty much everything else, but I thought I'd report while noticing it and maybe it's a good beginner UI contributor bug.