You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create an abstract pointer API that handles the state of pointer devices. See #714
It shall be used to internally replace our implementations of pointer related APIs.
Press and release mouse buttons
This should be analog to the keyboard implementation.
Move the pointer
This will be limited by the fact that our primary target environment jsdom has no layout.
But like we already support hover we should add the option to
Move the pointer from one element to another.
This should trigger the appropriate leave and enter events on the related targets.
This will neglect that we do not know the layout relation between those elements, i.e. if the elements will be rendered beside each other and moving the pointer will therefore be possible or if one renders over the other or outside of the viewport.
This will also neglect any other elements that might render between the two elements and therefore would also receive pointer events in a browser environment.
Move the pointer to specified coordinates on the element.
As for moving the pointer from one element to another, testing this with userEvent can not give confidence that the layout allows such movement. But it can be used to ensure that event handlers are correctly wired and work in principle.
The text was updated successfully, but these errors were encountered:
Create an abstract pointer API that handles the state of pointer devices. See #714
It shall be used to internally replace our implementations of pointer related APIs.
This should be analog to the
keyboard
implementation.This will be limited by the fact that our primary target environment
jsdom
has no layout.But like we already support
hover
we should add the option toThis should trigger the appropriate
leave
andenter
events on the related targets.This will neglect that we do not know the layout relation between those elements, i.e. if the elements will be rendered beside each other and moving the pointer will therefore be possible or if one renders over the other or outside of the viewport.
This will also neglect any other elements that might render between the two elements and therefore would also receive pointer events in a browser environment.
As for moving the pointer from one element to another, testing this with
userEvent
can not give confidence that the layout allows such movement. But it can be used to ensure that event handlers are correctly wired and work in principle.The text was updated successfully, but these errors were encountered: