Raise pointer events on captured element #18420
Merged
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?
Alternative to #15357 - please read that PR for a better understanding of the underlying issue.
As noticed in #15357 (comment), completely ignoring the capture leads to some unexpected behavior, such as any control reacting to the mouse moving over, even if they aren't really clickable.
This PR changes the logic to better match UWP: pointer events are now raised for the captured element.
Note that contrary to UWP and Win32,
PointerMoved
is still only raised when the pointer is directly over the captured element.We should consider changing that in another PR if needed.
An existing unit test has been updated.
Fixed issues