MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[WinUI3] Support continuous mouse event from web content to the native window

Open
#1,321 7 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request tracked
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

Is your feature request related to a problem? Please describe.
I create a small webapp that allows dragging to arrange the shapes (https://d2phap.github.io/shape-arrangement/), and I want to bring this to Webview2. However, the mouse event is not captured when I move the cursor out of the Webview2
Steps:

  • Click and hold on a shape
  • Still hold and drag the shape
  • Move cursor out of the window (or the Webview2)
  • The shape is not followed the cursor anymore

image

Describe the solution you'd like and alternatives you've considered

  • There should be an API / option to allow the cursor continue to capture out of the webview2
  • This will remove the gap of native app and webview2 app

AB#33613498

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the drag scenario in the WinUI3 WebView2 web content and observe where mouse capture stops when the cursor leaves the WebView2 or native window. Define completion as continuous delivery of the drag-related mouse events outside the webview, with no source files or tests named in the issue to guide implementation.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.