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
3.6.0 - click event not firing when mouseup and mousedown are different elements #5578
Labels
type: regression
A bug that didn't appear until a specific Cy version release
Comments
2 tasks
cypress-bot
bot
added
stage: work in progress
stage: needs review
The PR code is done & tested, needs review
and removed
stage: work in progress
labels
Nov 1, 2019
jennifer-shehane
added
the
type: regression
A bug that didn't appear until a specific Cy version release
label
Nov 6, 2019
cypress-bot
bot
added
stage: pending release
and removed
stage: needs review
The PR code is done & tested, needs review
labels
Nov 6, 2019
The code for this is done in cypress-io/cypress#5580, but has yet to be released. |
This is hitting us on quite a few tests while trying to upgrade to 3.6.0. Is there a plan to release soon? (am also blocked by critical issues in 3.5.0) |
@lukeapage yes, we're working to get a 3.6.1 release out ASAP |
Released in |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
currently, if the same element does not receive both the mouseup and mousedown, we do not fire the
click
eventThe correct behavior is to fire the click event to the
commonAncestor
element.This is a regression introduced in
3.6.0
The text was updated successfully, but these errors were encountered: