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
An increasing number of our users applies this library in test environments which support layout.
In those environments given the clientX/clientY coordinates of a pointer device, we could detect the target of pointer interactions automatically and improve the confidence our users get from their tests.
Suggested solution
If a user supplies x/y coordinates for pointer interactions, determine related DOM node(s) and position automatically.
If a target and or node/offset is given and contradicts the determined element/position, throw an error.
Todo
It would be great if we could support not declaring a target in the API call.
So far we reuse the previous pointer position for subsequent pointer actions. This begs the question how we would determine if we keep the coordinates and/or the target as a reference point.
The text was updated successfully, but these errors were encountered:
Problem description
An increasing number of our users applies this library in test environments which support layout.
In those environments given the
clientX
/clientY
coordinates of a pointer device, we could detect the target of pointer interactions automatically and improve the confidence our users get from their tests.Suggested solution
If a user supplies
x
/y
coordinates for pointer interactions, determine related DOM node(s) and position automatically.Document.elementFromPoint()
.Document.caretPositionFromPoint()
orDocument.caretPositionFromPoint()
.If a
target
and ornode
/offset
is given and contradicts the determined element/position, throw an error.Todo
It would be great if we could support not declaring a
target
in the API call.So far we reuse the previous pointer position for subsequent pointer actions. This begs the question how we would determine if we keep the coordinates and/or the target as a reference point.
The text was updated successfully, but these errors were encountered: