Skip to content
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

Support for passive events is not actually checked #6930

Merged
merged 1 commit into from
Dec 6, 2019

Conversation

Ivan-Perez
Copy link
Contributor

The passiveEvents variable was always a truthy value since it holds a reference to the function, instead of it being self-invokated and thus getting its result.

The `passiveEvents` variable was always a truthy value since it holds a reference to the function, instead of it being self-invokated and thus getting its result.
Copy link
Member

@mourner mourner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow, I have no idea how we missed that. Awesome catch, thanks so much!

@mourner mourner merged commit 472407c into Leaflet:master Dec 6, 2019
Schleuse pushed a commit to Schleuse/Leaflet that referenced this pull request Jan 13, 2020
The `passiveEvents` variable was always a truthy value since it holds a reference to the function, instead of it being self-invokated and thus getting its result.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants