Web session mouse input tracks incorrectly after display change
Hello, all! I've noticed an inconvenient issue that may or may not be a bug.
Expected Behavior
Mouse movement and input is tracked normally inside web sessions, allowing you to accurately click and interact with content inside the web session, even after a display change has occurred on the device running RDM.
Actual Behavior
Mouse movement is tracked incorrectly and input does not work after a display change as occurred on the device running RDM.
First Recognized Occurrence
This issue appears to have existed as long as our company has been using RDM, which goes back to at least 2022.x.x.
I can currently reproduce the issue in my environment:
Software
Hardware
Steps to Reproduce
Troubleshooting
I've tested and this appears to happen only in this direction. If you have RDM open and disconnect your laptop from a dock, web sessions appear to track mouse movement and input correctly.
Additionally, I tested this with a slightly different hardware setup and was able to replicate the issue the same using:
I had hoped that simply closing the session and re-opening it would resolve the issue, however it does not.
Workaround
In the meantime, closing RDM entirely and re-opening it appears to resolve the issue.
If this is indeed some kind of bug, I hope that some of the above information is helpful. If not a bug and this is expected behavior, I will pass that information along to our team. Thanks!
--
Griffeth Barker
๐ป Call/Chat on Microsoft Teams
๐ง Send me an email
๐ Connect on LinkedIn
Hello Griffeth,
Thank you for contacting us on that matter.
We will try to reproduce this behaviour on our side.
If we are successful in this investigation, I will post here.
If not, I will open a case to exchange information on your configuration.
Best regards,
Patrick Ouimet
Hi, Patrick,
I've just noticed something that might indicate this is a bug with Microsoft Edge WebView 2, rather than with Remote Desktop Manager. The "New Outlook" which I believe uses WebView, also suffers from this same issue in the same scenario. I suppose it could still be an issue with Remote Desktop Manager, but it could also be a bug with the WebView2 dependency.
Just wanted to provide that new discovery. Thank you!
--
Griffeth Barker
๐ป Call/Chat on Microsoft Teams
๐ง Send me an email
๐ Connect on LinkedIn
Hello Griffeth,
Thank you for this information about Webview2.
We will investigate this, and I will let you know as soon as we have any results.
Best regards,
Patrick Ouimet