Web-UI Mouse Input Issues on Android

[jonasprokopf]

qBittorrent & operating system versions

Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-112-generic x86_64)/Android 14
Firefox Android 127.0.1
qBittorrent v4.6.5 Web UI (64-bit)
libtorrent-rasterbar: I can't really tell, I just installed the latest Qbit from the repo. I don't think it's relevant either.

What is the problem?

Hi, I am hosting qb on my Ubuntu server at home, and when I'm away for most of the week, I like to control it through its excellent web interface on my android tablet with a touchpad and thus mouse inputs. However, I find it very difficult controlling it, since approximately 9/10 mouse inputs don't register. Actually, the issue got much worse after I upgraded to the latest version, unfortunately, I don't know from which build. What's more, scrolling is also impossible unless some specific circumstances are met which I don't really understand - so I always have this dance of selecting a bunch of torrents from the list, long clicking them to reveal the context menu, then clicking on a single one again - intermittendly trying to scroll, until it eventually works. Another problem is that selecting multiple torrents is only possible when pressing shift + mouse 1 on my keyboard pack (keyboard & touchpad), not my pressing shift on the keyboard and selecting torrents through the touch screen, which would be preferrable, since using touch controls is much more responsive than mouse inputs. I'm experiencing these issues on Firefox Android 127.0.1, regardless of whether I tell Firefox to load the "mobile" or the desktop site. However, I'm also experiencing similar issues on Chrome.

I don't know how much you are interested on fixing these issues for my admittedly niche use case, but it would certainly be much appreciated.

Steps to reproduce

Try using the web ui on an Android device with a mouse and keyboard.

Additional context

No response

Log(s) & preferences file(s)

I don't know, would logcat be helpful?

[USBhost]

It's an issue ever since iirc they make the js scripts strict or something. This was back in 3.3.x and since been bad ever since (3.4+). Note im talking about touch input not mouse like you. However if your tablet makes it register as a touch input then it will be hit by the same problem.

My best recommendation is to use one of those apps that use the API to control it on the play store.

[jonasprokopf]

It's an issue ever since iirc they make the js scripts strict or something. This was back in 3.3.x and since been bad ever since (3.4+). Note im talking about touch input not mouse like you. However if your tablet makes it register as a touch input then it will be hit by the same problem.

My best recommendation is to use one of those apps that use the API to control it on the play store.

Thanks, but that's not an option for me, because I have a dynamic IP.