Ignore pointer capture for PointerEntered and PointerExited events following UWP behavior #15357
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does the pull request do?
This one is interesting, and might not be an expected behavior for some (including me).
But after testing #15293 on UWP, I noticed that they handle PointerExited event differently from how we do.
Bonus change: fixed devtools incorrectly reporting events that reuse the same RoutedEventArgs instance.
What is the current behavior?
In Avalonia before this PR it looked like:
What is the updated/expected behavior with this PR?
In UWP behavior looks like:
After this PR, Avalonia behavior is the same as in UWP. Aside from automatic capturing on pointer pressed.
Checklist
Breaking changes
Behavioral change.
Fixed issues
Fixes #15293