Closed jrandolf closed 1 year ago
For a wheel
action in the WebDriver classic specification we define values like:
If x is less than 0 or greater than the width of the viewport in CSS pixels, then return error with error code move target out of bounds.
To stay compatible with classic WebDriver BiDi also has to use CSS pixels and not screen pixels.
Turns out there was a bug in Chromium. Fixed in https://chromium-review.googlesource.com/c/chromium/src/+/4813942
Currently BiDi doesn't specify whether scrolling uses hardware pixels or CSS pixels. Based on current implementation, it seems like we want hardware pixels.