MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Pointer lock - unexpected, large movementX/Y when in webview2
@tochukwuIbeEkeocha is already working on this.
Since Oct 20, 2023.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
What happened?
Using pointerlock API https://w3c.github.io/pointerlock/ we see a buggy behavior on certain machines in our development team, even though we all have the same model, OS:
Can be reproduced with the pointer lock demo: entering pointer lock and moving the mouse slowly inside the canvas. This should result in a smooth movement and only minimal values in movementX/Y event. But on some machines we see large jumps, see video "BugCase". On the same machine with the same WebView2 runtime as Edge, the demo running inside edge browser does not show those jumps, see "PointerLockDemoInMsedge". Seen in our own Win32 app but can also be reproduced with the WinForms browser.
Same demo running in MS Edge browser:
Importance
Blocking. My app's basic functions are not working due to this issue.
Runtime Channel
Stable release (WebView2 Runtime), Prerelease (Edge Canary/Dev/Beta)
Runtime Version
118.0.2088.46
SDK Version
2106.0
Framework
Win32
Operating System
Windows 10
OS Version
10.0.19045
Repro steps
Use WebView2WindowsFormsBrowser from WebView2 examples and replace the assets with those here, then click the "Test pointer lock" link below the heading. Enter pointer lock by clicking into the canvas and move mouse slowly in the canvas region, on some machines we see large jumps (watch the movement values in the upper right).
Regression
Don't know
Last working version (if regression)
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.