Skip to content

[Problem/Bug]: mouseleave doesn't fire on leaving client anymore #5232

Closed
@Anutim

Description

@Anutim

What happened?

Since today (was working fine yesterday), the mouseleave event doesn't fire upon leaving the client area. (e.g. if you're attaching a listener to document.body), to make it work now you'd need to set margin/padding on the body)

It still behaves normally if you're holding down a mouse button pre-mouseleave however.

I have also checked older untouched projects, with their own separate data directory, and it's affected on all of them, so I'm pretty sure it's due to a WebView2 update.

Importance

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

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

136.0.3240.50

SDK Version

No response

Framework

Other

Operating System

Windows 11

OS Version

26100.2314

Repro steps

Attach a mouseleave listener to document.body and watch it not get fired upon mouse leaving the window.
(Assuming there's no margin/padding)

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Regression in newer Runtime

Last working version (if regression)

I don't know, probably any before the mentioned runtime?

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingregressionSomething used to work but doesn't anymore

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions