Are you using stock Docker compose setup?
No
If not, either reproduce this issue on the official demo or switch to Docker and see if the issue is resolved.
Describe the problem you’re having:
After commit 98251022d4, unread count on some feed is incorrect
Include steps to reproduce the problem:
Removed all user css customize
Update to lastest commit (0f6644880a)
Refressh ttrss
In feed tree, if the feed tree width is small enough, unread count on some feed is cut off when feed title is long (shown as {something}…) and the feed count is more than 3 digits (1000 and up)
Revert back to the commit before it (334a361e79)
Refressh ttrss
Unread count showed up correct again
tt-rss version (including git commit id):
0f6644880a
Platform (i.e. Linux distro, PHP, PostgreSQL, etc) versions:
Debian 10 Buster, PHP 7.3, PostgreSQL 11
Please provide any additional information below:
I reviewed the 98251022d4 commit. Seem like the most likely problem is the addition of dijitTreeRowFlex class but not sure how it affects the rendering.
Changing the body.ttrss_main #feeds-holder #feedTree .dijitTreeNode .dijitTreeRow .counterNode, min-width from 23px to auto fixed this but the nice, uniform width counterNode box is no longer possible.
fox
2
you’re reporting a web browser issue and haven’t mentioned anything about it at all. not even a screenshot.
Sorry fox, I forgot the screenshot.
My browser version is Chrome 87.
Also my mistake, it looks like 4 digits (10000 range), not 3.
fox
4
your screenshot looks more like 6 digits. 
e: what if we clip those to 9999 or something?
either that or hide/ellipsize overflow but it looks bad 
I have something like this for now but it’s still look butt ugly
CSS:
body.ttrss_main #feeds-holder #feedTree .dijitTreeNode .dijitTreeRow .counterNode {
min-width: auto;
padding: 0px 5px !important;
}
fox
6
https://git.tt-rss.org/fox/tt-rss/commit/c34a4c85bde242c991baf1f383694e9a4fa82940
Q: but I NEED to see the exact value for my 255648 unread articles 
A: make a plugin which adjusts Feeds._max_counter_value (while simultaneously increasing min-width of .counterNode i guess)
Lol, yes yes. Now all my feeds look like those maxed out value in those old video game. 
levito
8
Hi @fox, i’d suggest adding flex-shrink: 0 to .counterNode. This fixes the styling without the need of clipping the value at 9999. You also don’t need to mess with increasing min-width then.
fox
9
