-
Notifications
You must be signed in to change notification settings - Fork 861
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 collision with bootstrap #67
Comments
+1 for this issue! |
+2! |
The fix is to remove this line, actually: $.extend($.support, support); |
Bootstrap doesn't seem to be respecting jQuery conventions. jQuery's documentation (here) seems to suggest that In any case, let me fix this. |
Test it out in v0.9.9, guys. |
This is still an issue with v0.9.9 and Bootstrap v3.1.1 |
I can confirm that this is still not working with Bootstrap 3.1.1 and Transit 0.9.9 |
Can anyone check out #143 and see if it fixes your problem? |
...that is, see if @isochronous's fork here works for you. As I don't have a bootstrap project easily-accessible right now to try it on, perhaps any of you kind folks can help me test it :) |
Yup, that fork resolves the issue. Thanks! On Fri, Apr 25, 2014 at 9:33 PM, Rico Sta. Cruz [email protected]:
Christopher Kennedy Part-time Haberdasher, full-time Crazy Cat Lady {one:bright:light} Google Voice: (415) 226-9663 |
Thanks! Will review it in a while and merge it in. |
I am using bootstrap and jquery.transit together on a project.
There is a naming collision in the way $.support.transition is used by both libraries.
Where transit does this:
Bootstrap does this:
As you can see, transit sets support.transition to a string while Bootstrap assigns an object literal. This is causing bootstrap modal to not work correctly when it searches for the $.support.transition.end property.
The text was updated successfully, but these errors were encountered: