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
{{ message }}
This repository has been archived by the owner on May 30, 2023. It is now read-only.
Description:
sendEvent('click', x, y) does not work when the point is outside the default viewportSize of width: 400 and height: 300.
Suggestion:
sendEvent should ignore viewportSize and work if the point is within the page width and height.
Disclaimer:
This issue was migrated on 2013-03-15 from the project's former issue tracker on Google Code, Issue #302.
🌟 4 people had starred this issue at the time of migration.
The text was updated successfully, but these errors were encountered:
It ought to set appropriate variables in the MouseEvent. Something like clientX = x%viewportWidth, pageX = x. There may be some tricky areas in here because of scrolling expectations.
Current work-around is simply to set the viewport height large enough to capture the click then set it back to a smaller height so the render doesn't overdraw the area.
In addition to it "not working" - if clicking outside the viewport area it will trigger a click event on the root HTML element with the correct clientX and clientY populated. but even if there is a valid element at those coords it will not be clicked.
I think at least a good temporary behavior would be to throw an error if trying to click outside of the viewport area. Right now there is no indication that anything has gone wrong.
Due to our very limited maintenance capacity (see #14541 for more details), we need to prioritize our development focus on other tasks. Therefore, this issue will be automatically closed. In the future, if we see the need to attend to this issue again, then it will be reopened. Thank you for your contribution!
kk7...@gmail.com commented:
Disclaimer:
This issue was migrated on 2013-03-15 from the project's former issue tracker on Google Code, Issue #302.
🌟 4 people had starred this issue at the time of migration.
The text was updated successfully, but these errors were encountered: