Currently, it appears that Cursor state requires the mouse to be moved to force it to re-evaluate the cursor instruction of what its hovered over.

In an event where what is displayed on-screen changes, and the mouse is not displaced, this can sometimes result in the mouse cursor displaying a cursor state for an Element that is no longer visible on-screen.

See attached video, where the Hand cursor can be seen persisting until it's moved.

Repro Steps:

1) Open Popup.xaml from the MiniShowcases Studio Project in the InternalProjects GitHub.
2) Play the Page using Ctrl+P

3) With the Page playing, click on the 'Open Popup' button in the middle of the Page, paying very close attention to not move the position of the mouse during, or after the click.

Observe how when hovering over the button, the mouse cursor displays the 'Hand' cursor.

Observe how after the button has been pressed, and the cursor is positioned in an area with no interactive elements, it continues to display the 'Hand' cursor.

4) Move the cursor by a tiny amount, without hovering over the 'Close' button in the Popup.

Observe how at the smallest amount of movement detected, the mouse shows the correct 'Arrow' cursor, demonstrating that it was indeed overlayed on top of an area where no 'Hand' cursor should have appeared.

Expected Results: The cursor always accurately reflects the cursor state befined by the Element it is directly over.