-
-
Notifications
You must be signed in to change notification settings - Fork 79k
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
Remove touchstart from bootstrap-dropdown.js. #6488
Conversation
+1 |
+1 Full disclosure: I'm the FastClick author. |
I wholeheartedly agree with removing touchstart from these. cc: #4550 (which is still broken for me) |
+1 for consistency sake, just encountered this as well. |
Remove touchstart from bootstrap-dropdown.js.
cool sounds good - thanks guys |
@nanek this pull request broke dropdowns for me, particular this line: .on('.dropdown-menu', function (e) { e.stopPropagation() }) which seems a bit strange to keep since you removed the event before .dropdown-menu which as touchstart before. |
Jeah updating to 2.3.0 also screwed up my dropdown menus. |
Fix approach is taken from Twitter Bootstrap 3.0 Twitter Bootstrap bug reports: twbs/bootstrap#4550 twbs/bootstrap#6488
Fix approach is taken from Twitter Bootstrap 3.0 Twitter Bootstrap bug reports: twbs/bootstrap#4550 twbs/bootstrap#6488
"Use case 2" in the documentation describes a compatibility issue with Twitter Bootstrap 2.2.2. After reading this, I was unsure about whether the issue only applied to version 2.2.2 or whether this workaround was still required. After some investigation, it appears that the compatibility issue was introduced in twbs/bootstrap@c9cef741 (included in `v2.1.0` and later) and was resolved in twbs/bootstrap@b5ad5068 (included in `v2.3.0` and later, including `v3.0.0`) as a result of twbs/bootstrap#6488. To avoid causing confusion for future users who may not know about the state of this issue, this commit clarifies which versions of Twitter Bootstrap are affected. Signed-off-by: Kevin Locke <[email protected]>
"Use case 2" in the documentation describes a compatibility issue with Twitter Bootstrap 2.2.2. After reading this, I was unsure about whether the issue only applied to version 2.2.2 or whether this workaround was still required. After some investigation, it appears that the compatibility issue was introduced in twbs/bootstrap@c9cef741 (included in `v2.1.0` and later) and was resolved in twbs/bootstrap@b5ad5068 (included in `v2.3.0` and later, including `v3.0.0`) as a result of twbs/bootstrap#6488. To avoid causing confusion for future users who may not know about the state of this issue, this commit clarifies which versions of Twitter Bootstrap are affected. Signed-off-by: Kevin Locke <[email protected]>
Causes dropdown events to trigger twice on mobile Reference: twbs#6488
It would be great to remove listening to touchstart from the bootstrap dropdowns. This would make it consistent with the rest of the bootstrap components.
It seems like either all clickable elements should be listening for touchstart or none of them should be. I agree with the comment from #3772 (comment)
FastClick works great with Bootstrap except for the bootstrap-dropdowns because they also listen for touchstart which then causes the dropdown to open and then immediately close. See ftlabs/fastclick#48 for more info. Removing touchstart from bootstrap dropdowns would fix this issue and make all of the bootstrap controls behave the same.
Thanks!