-
Notifications
You must be signed in to change notification settings - Fork 63
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
[Question] e.stopImmediatePropagatio() really need? #55
Comments
vlukyanoff
changed the title
[QUESTION] e.stopImmediatePropagatio() really need?
[Question] e.stopImmediatePropagatio() really need?
Sep 15, 2017
Hi @vlukyanoff, did #56 fix the issue? (v1.5.3) |
Hi @noeldelgado! Yes, it fixed the issue. Thank you! |
@noeldelgado, could you update dependency in https://github.com/noeldelgado/react-gemini-scrollbar please? |
I would be great if gemini-scrollbar were peerDependency of react-gemini-scrollbar to avoid such update needs. |
@vlukyanoff done, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, @noeldelgado!
I can't use mouseDown event on block with gemini scrollbar because gemini call e.stopImmediatePropagation() in _startDrag function.
I know, stop propagation isn't best practice, because it changes standart behavios of the browser.
Maybe, is there way to avoid stop propogation in this case?
gemini-scrollbar/index.js
Line 371 in 88c5d04
The text was updated successfully, but these errors were encountered: