Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

3.6.0 - click event not firing when mouseup and mousedown are different elements

See original GitHub issue

currently, if the same element does not receive both the mouseup and mousedown, we do not fire the click event

The correct behavior is to fire the click event to the commonAncestor element.

This is a regression introduced in 3.6.0

Issue Analytics

State:
Created 4 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

lukeapagecommented, Nov 7, 2019

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)

0reactions

cypress-bot[bot]commented, Nov 8, 2019

Released in 3.6.1.

Top Results From Across the Web

When a mousedown and mouseup event don't equal a click

I had problems with click events not firing and it turned out to be due to the mousedown and mouseup events not firing...

jQuery API Documentation

jQuery is a fast, small, and feature-rich JavaScript library. It makes things like HTML document traversal and manipulation, event handling, animation, and Ajax ......

Replace live() with on() in jQuery - GeeksforGeeks

When the user clicks the anchor element, the event is triggered to the root ... “click” event is attached with given “p” and...

UI Events - W3C

The load event is queued to be fired asynchronously at the script element. However, because it is an async event, its order with...

Element: mousedown event - Web APIs | MDN

Note: This differs from the click event in that click is fired after a full click action occurs; that is, the mouse button...