Open whimboo opened 10 months ago
The Browser Testing and Tools Working Group just discussed Perform Actions: "scroll" action incompatible with pointer origin type
.
jgraham: So that raises the question of why `scroll` isn't an action on a `pointer`? Is it worth making `scroll` an action on a `pointer` type or not? q+ ack next shs96c: I think it probably is
@shs96c, I assume that means that to keep backward compatibility we should leave the wheel
input device with the scroll
action but also make it available for the pointer
device?
The Browser Testing and Tools Working Group just discussed Backward compatibility for "get coordinates relative to an origin" fails for "wheel.scroll" actions and a "pointer" origin
.
someone (@whimboo?) should edit make webdriver/tests/classic/perform_actions/wheel.py
check clientX
/clientY
, with/without mouse move actions before the wheel action? and then we can observe existing behaviour here
The problem is that a Wheel input source in the WebDriver classic specification does not have
x
andy
coordinates. But then we run into a problem inget coordinates relative to an origin
. Here thex
andy
properties of the input source need to be used to calculate the target points.Ideally the current position of the pointer should be used, but given that it is a different input type there is no access to it. On #1409 the proposal was made to add the
scroll
action to thepointer
input type, and that would have allowed us to actually work with the current pointer position.Right now both
start x
andstart y
of ascroll
action always refer to0, 0
which is similar to theviewport
origin.Having
scroll
as action for apointer
input device would also make it much more simpler to handle in case of multiple pointer input devices.