MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Complete keyboard/mouse input filtering API
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
I'd like to see (and possibly reject) all keyboard and mouse input going to the WebView.
add_AcceleratorKeyPressed is good, but incomplete. It would be great if it routed full input message range, WM_MOUSEFIRST to WM_MOUSELAST and WM_KEYFIRST to WM_KEYLAST.
Alternatively, expose a HWND that can be subclassed for filtering purposes.
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
Start by reviewing the existing add_AcceleratorKeyPressed API and the requested Windows message ranges, WM_MOUSEFIRST to WM_MOUSELAST and WM_KEYFIRST to WM_KEYLAST. Compare that approach with exposing an HWND for subclassing; done means agreeing on and implementing a complete, usable input-filtering API for WebView2.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100