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
#68 don't close RootCloseWrapper on right clicks #69
Conversation
|
||
simulant.fire(document.getElementById('my-div'), 'click', {button: 1}); | ||
|
||
expect(spy).to.have.been.called; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be the opposite, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, thanks
@@ -10,6 +10,14 @@ const CLICK_WAS_INSIDE = '__click_was_inside'; | |||
|
|||
let counter = 0; | |||
|
|||
function isLeftClickEvent(event) { | |||
return event.button === 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NIT: Do we use semicolons in this repo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why so strict when semicolon insertion keeps you safe? :-)
http://www.ecma-international.org/ecma-262/5.1/#sec-7.9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but we still want consistency in code style.
LGTM |
LGTM. @adamziel mind squashing? |
@taion squash :-) |
I'll squash and merge by hand then. |
Merged in f1528af. |
@jquense Can this be v0.6.1? |
sure, no time to release now tho for me. |
re #68