Describe the bug
A clear and concise description of what the bug is. Ideally with a screenshot if applicable.
when testing out the latest build on a surface pro (client) from my desktop (server), i tested out the "block remote input" feature. i was still able to control keyboard/mouse on the client. is this suppose to block input on client's computer?
To Reproduce
Steps to reproduce the behavior:
On server computer, while connected to a client, click on "Block Remote Input"
Remotely Version
Server (can be found on about page): 2024.02.23.1927
Expected Behavior
if Block Remote Input is enabled, client should not be able to use keyboard/mouse until server is disconnected.
Desktop (please complete the following information):
OS: [e.g. iOS] Windows 11 Pro
Browser [e.g. chrome, safari] Edge
Version [e.g. 22] Version 122.0.2365.80 (Official build) (64-bit)
[ X ] I am running Remotely in Docker and not on my QNAP, Synology, or Internet Connected Toaster
Describe the bug A clear and concise description of what the bug is. Ideally with a screenshot if applicable.
when testing out the latest build on a surface pro (client) from my desktop (server), i tested out the "block remote input" feature. i was still able to control keyboard/mouse on the client. is this suppose to block input on client's computer?
To Reproduce Steps to reproduce the behavior: On server computer, while connected to a client, click on "Block Remote Input"
Remotely Version Server (can be found on about page): 2024.02.23.1927
Expected Behavior if Block Remote Input is enabled, client should not be able to use keyboard/mouse until server is disconnected.
Desktop (please complete the following information):