mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
WebUI: Make virtual table rendering the default #17514
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#17514
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Piccirello on GitHub (Feb 19, 2026).
Virtual rendering (#22502) provides a performance boost by only rendering the rows that are visible on screen (plus some buffer). The performance improvement is particularly notable when a user has thousands of torrents, or when an individual torrent has thousands of files. Virtual rendering has been supported by all tables since #23544.
I'd like to use this issue to track any blockers to making virtual rendering the default in the WebUI. Once all known issues are resolved, we should switch to virtual rendering and remove the non-virtual implementation.
Known issues:
@Piccirello commented on GitHub (Feb 19, 2026):
cc @tehcneko @HanabishiRecca @sk0merko
@HanabishiRecca commented on GitHub (Feb 19, 2026):
Never used it due to being broken in Firefox, so can't comment on that.
@tehcneko commented on GitHub (Feb 20, 2026):
I think #23861 should fix that?
I was going to open a pull request to enable it by default since 5.2 was branched, hoping people could test it more. I don't know if this is a good idea, though.
@HanabishiRecca commented on GitHub (Feb 20, 2026):
Maybe, I reported it back in the original PR https://github.com/qbittorrent/qBittorrent/pull/22502#issuecomment-2817328814
@Piccirello commented on GitHub (Feb 20, 2026):
#23861 does fix that issue you originally reported. I've tested virtual rows on Firefox and couldn't find any other issues, besides that and #23860. Please test and let me know if you run into anything else.
I think enabling it by default in master makes sense, once the two PRs above are merged. That'll give us ample time to test before 5.3 is branched. Ultimately we'll want to fully remove the non-virtual logic before 5.3 is branched so that virtual rows are the only supported implementation.
@HanabishiRecca commented on GitHub (Feb 20, 2026):
Another issue I found (with the patches applied): keyboard arrow navigation doesn't work.
@Piccirello commented on GitHub (Feb 20, 2026):
I was able to partially reproduce. Up/down navigation works at first, but only until rows are updated (e.g. next
/filesfetch). Left/right in the content table doesn't work at all.@HanabishiRecca commented on GitHub (Feb 20, 2026):
Actually yes, it works until the first update. Hardly noticable with 1 second update interval though.
@Piccirello commented on GitHub (Feb 20, 2026):
Fixed in #23865