-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
trigger('mousemove', ...) yields undefined values for screenX and screenY in event handler #3187
Labels
Comments
@fr0 thanks for pointing this out, I'll put it in the mix for synthetic mouse fixes |
28 tasks
cypress-bot
bot
added
stage: needs review
The PR code is done & tested, needs review
stage: work in progress
and removed
stage: work in progress
stage: needs review
The PR code is done & tested, needs review
labels
Aug 8, 2019
cypress-bot
bot
added
stage: needs review
The PR code is done & tested, needs review
and removed
stage: work in progress
labels
Sep 6, 2019
cypress-bot
bot
added
stage: work in progress
stage: needs review
The PR code is done & tested, needs review
and removed
stage: needs review
The PR code is done & tested, needs review
stage: work in progress
labels
Sep 25, 2019
cypress-bot
bot
added
stage: needs review
The PR code is done & tested, needs review
and removed
stage: work in progress
labels
Oct 7, 2019
cypress-bot
bot
added
stage: pending release
and removed
stage: needs review
The PR code is done & tested, needs review
labels
Oct 11, 2019
The code for this is done in cypress-io/cypress#3030, but has yet to be released. |
Released in |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current behavior:
Triggering
mousemove
via.trigger
correctly fills inpageX
,pageY
,clientX
, andclientY
. However, Cypress fails to fill in thescreenX
andscreenY
values.This can cause erroneous behavior if the application depends on them.
Desired behavior:
screenX
andscreenY
should probably just have the same values asclientX
andclientY
.Versions
3.1.4
The text was updated successfully, but these errors were encountered: