-
-
Notifications
You must be signed in to change notification settings - Fork 78.9k
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
Use a more individual event namespace #10848
Comments
Such a change could not be made until v4 due to backward compatibility. |
I already thought so. But it would be nice to keep it in mind for v4. |
@cvrebert why not create a v4 milestone to group this kind of proposals? |
+1 i would like to see this fixed |
Added to our internal v4 planning document. |
I spent some time digging into the conflict with Prototype and the 'hide' event. Here's an explanation of why it happens, which I just posted on stackoverflow: I think there might be a solution -- Maybe not so hard... I haven't tested this, it's just an idea: Instead of (excerpted from tooltip.js):
maybe something like
|
This issue is based on #8379 and #6921 and the request of @mdo to open a new issue for it.
Bootstrap 3.0 is using an event namespace, what is great. For example:
var e = $.Event('hide.bs.' + this.type)
But this namespace is not really individual. Because of the point it can be identical with the
hide
event of other libs. For example prototype (see #8379).I know that bootstrap does not support other libs, but if it is using a namespace it would make sense to make it unique.
The solution could be to change the event name, eg, 'bs:hide.' + this.type (to use Backbone-inspired namespacing).
The text was updated successfully, but these errors were encountered: