Open Youssef1313 opened 2 months ago
The ContentDialog test change done in #17633 is caused by this issue. It may be best to revert the test change when this issue is resolved.
The ContentDialog test change done in #17633 is caused by this issue. It may be best to revert the test change when this issue is resolved.
Hummm for me it was only the focus of the button that has change, when the Dialog
is being opened:
and then when we have tapped on the overlay:
I think that's more the "hover" state, which happens because of the missing pointer exit event. The repro in the issue probably makes it more clear?
In the first screenshot, the button is in PointerOver visual state.
Current behavior
Use this XAML:
and code-behind:
If you click the button, and don't move the mouse, you'll find that it's stuck in PointerOver state, while it should have been in Normal state. The root cause is that we are missing PointerExited event in this case.
Expected behavior
In WinUI, they have a special internal
XCP_POINTERUPDATE
event. They request it by callingRequestReplayPreviousPointerUpdate
, and then this event will raise the relevant events, if needed.How to reproduce it (as minimally and precisely as possible)
No response
Workaround
No response
Works on UWP/WinUI
None
Environment
No response
NuGet package version(s)
No response
Affected platforms
No response
IDE
No response
IDE version
No response
Relevant plugins
No response
Anything else we need to know?
No response