MicrosoftEdge / MicrosoftEdge/WebView2Feedback
WebView2 swallows mouse wheel events
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Description
Since adding webview2 to my application, the WndProc(...) function in my window does not receive WM_MOUSEWHEEL messages anymore.
I tried toggling AreBrowserAcceleratorKeysEnabled, IsSwipeNavigationEnabled and IsZoomControlEnabled1 in CoreWebView2Settings, but it didn't change anything.
Version
SDK: 1.0.2065-prerelease (before: last official nuget release)
Runtime: 116.0.1938.69
Framework: WPF
OS: Win10
Regression
unknown
Additional context
Depending on modifier keys, the mouse wheel should be handled by the JS app or the .NET app.
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.
Research direction
Reproduce the behavior in the WPF application and inspect the window WndProc alongside the CoreWebView2Settings options mentioned in the report. Verify how WM_MOUSEWHEEL is routed for different modifier keys and whether the JS app or the .NET app receives each event.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- desktop, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100