MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: WebView2CompositionControl not firing mouseleave and dragover events

Open
#5,676 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What happened?

I am using WebView2CompositionControl in a WPF app (.NET 10). If I have an js application inside, which is using mouseleave (pointerleave) or dragover events, it is not working properly (they are not firing). If I use the WebView2 control, everything is working.

You can find the reproducable example in this repo: https://github.com/DAST-Synchronics/WebView2CompositionBug

Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

1.0.4129.50

SDK Version

151.0.4129.86

Framework

WPF

Operating System

Windows 11

OS Version

10.0.26200

Repro steps
  1. Clone the following repo - https://github.com/DAST-Synchronics/WebView2CompositionBug and start it
  2. You will get two windows, one with WebView2CompositionControl and one with WebView2 and DevTools opened. There is a simple html/js example, in which you can test the functionality. The mouse and drag events are automatically logged. As you can see, in the case of the WebView2CompositionControl the mouseleave and dragover events are not logged, in case of the WebView2, everything works.
Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

No, this never worked

Last working version (if regression)

No response

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

Clone and run the WebView2CompositionBug repository, then compare the WebView2CompositionControl window with the WebView2 window and its logged mouse and drag events. Start with the WebView2CompositionControl and the HTML/JavaScript example; done means mouseleave/pointerleave and dragover events behave like they do in the regular WebView2 control.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.