qBittorrent
qBittorrent copied to clipboard
qbittorrent
WEBUI: torrent list hidden on chrome-based browser
qBittorrent & operating system versions
qBittorrent: 5.0.0 x64 Operating system: Arch linux Qt: 6.7.3 libtorrent-rasterbar: 1.2.19.0
Browsers tested NOT OK: Brave version: Version 1.70.119 Chromium: 129.0.6668.70 (Official Build) (64-bit) Chrome version: Version 129.0.6668.70 (Official Build) (64-bit)
Browser tested OK: firefox version: 130.0.1 (64-bit)
What is the problem?
The torrents' list is hidden/collapsed by default on chrome based browser:
I have to select the separator between "General, Trackers, Peers..." and "Transfers, Search, RSS" to increase the zone height. It looks like be default this zone is collapsed to the minimum height. Each time I reload the page, it collapsed to the minimum again.
Steps to reproduce
- Load the homepage of the WebUI with a chrome-based browser
Additional context
No response
Log(s) & preferences file(s)
No response
In the new version 5.0.0 of the web interface, only the first part of the leftmost table, "Status," works visually correctly. When clicking on the buttons "All," "Loading," etc., up to "Error," the text color changes from black to white, which prevents it from blending in with the blue background indicating the currently selected button. Below, starting from the "Categories" section, the text remains black when clicked and blends in with the blue highlight
this is how it looks on the standard program theme
I didn't contribute to 5.0 pretty much at all but I"m pretty sure both of these issues were fixed in master some time ago as part of other things. They are pretty annoying little bugs @glassez and I could PR fixes for both of them tomorrow. But I don't know what exactly is the process here, should I PR both of them to your branch like last time?
But I don't know what exactly is the process here, should I PR both of them to your branch like last time?
I suppose you're talking about backporting previously merged PRs. I can add them to backport PR myself (knowing which PRs are in question) if they do not have merge conflicts. However, I often cannot confidently resolve such conflicts, because I am not very competent in WebUI code.
Yes, but I can't remember and check which one right now. I could make targeted fixes specifically for 5.0, pretty sure only 2 lines are needed to be changed IIRC - it would be much easier.
I could make targeted fixes specifically for 5.0, pretty sure only 2 lines are needed to be changed
Ok.
I have this problem in Safari. Very annoying. I left this info in PR comment, but will duplicate here also: In the master it was fixed by #21209
