-
Notifications
You must be signed in to change notification settings - Fork 414
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Torrent table row header not always aligned with column #2794
Comments
@jevenski once this is fixed, we can post Beta 5. And possibly the stable |
This issue existed before v5, and is because of the internal structure of |
Thanks for checking this. Let's leave it as is for now and move forward. |
Alright, target adjusted for |
- Merge stable-head and stable-body into one HTML table, and thus removes the process to sync horizontal scroll position. - Fix table header split away from table body when scrolled to right end (Novik#2794). - Adjust internal styles of the s-table to fit the new table structure.
* Merge stable head and body into one table - Merge stable-head and stable-body into one HTML table, and thus removes the process to sync horizontal scroll position. - Fix table header split away from table body when scrolled to right end (#2794). - Adjust internal styles of the s-table to fit the new table structure. * Fix various bugs - Fix move header display postion error. - Fix table sorting on mobile screens. - Fix tracker icon display issue (#2849).
Please complete the following tasks.
Tell us about your environment
Web Browser: Google Chrome 130.0.6723.117
ruTorrent: master: c6caa69
PHP: PHP 7.4.3
OS: Ubuntu 20.04.6 LTS
web server: lighttpd/1.4.55
Tell us how you installed ruTorrent
git clone https://github.com/Novik/ruTorrent
Describe the bug
When we scroll the torrent table all the way to the right, the header row is not aligned with the column.
Steps to reproduce
Scroll the torrent table all the way to the right.
Expected behavior
The header row is aligned with the column.
Additional context
No response
The text was updated successfully, but these errors were encountered: