The no-conflict mode should be the default behaviour

[thewebdreamer]

The no-conflict mode should be the default behaviour. Why would a Bootstrap client need to implement this?

[cvrebert]

I believe no-conflict-is-not-the-default is the norm for jQuery plugins?

[thewebdreamer]

It is true that it is the norm for jQuery plugins.

Couldn't there be a clash with other jQuery plugins with the current implementation of Bootstrap though?

[hnrch02]

Couldn't there be a clash with other jQuery plugins with the current implementation of Bootstrap though?

That is precisely what noConflict was made for.

[cvrebert]

Indeed, we know for a fact that such clashes exist (e.g. with jQuery UI). One could equally ask why jQuery UI isn't no-conflict-by-default.

However, other than providing a working .noConflict, we explicitly don't officially support using 3rd-party libraries; see the warning box under http://getbootstrap.com/javascript/#js-events . Resolving inter-library conflicts is something the user must deal with themselves.

[thewebdreamer]

My understanding was that jQueryUI is already by default non clashing by using a "ui" prefix in their CSS and by using namespaces in their plugins.

Anyway, it doesn't mean that Bootstrap must do what others are doing. Otherwise, you can close this.

[cvrebert]

jQuery UI doesn't seem to be using no-conflict in their JS by default; e.g. the example on http://jqueryui.com/tooltip/ simply does

$(function() {
  $( document ).tooltip();
});

un-namespaced, same as Bootstrap.

[hnrch02]

Well, I suppose you could namespace Bootstrap's JavaScript plugins by assigning them to $.fn.bootstrap.<something> or $.fn.bs.<something> but as this is a de facto non-existent pattern and—as @cvrebert stated—Bootstrap doesn't officially support any third party libraries, I see no reason for Bootstrap to adopt it.

[thewebdreamer]

@cvrebert: I've downloaded the latest jQueryUI located at http://jqueryui.com/download/all/ to validate this.

What, I've found is that each plugin is within a closure and the non conflicting jQuery variable is passed as a parameter. The $ is only an alias within the context of the closure. You can find a very old bug ticket confirming this: http://bugs.jquery.com/ticket/1686.

From what I see Bootstrap is also doing this, but nothing is namespaced. The difference that I see is that jQueryUI is namespaced and they use a helper function called "widget" to add their plugins. They pass the name of the plugin to "widget" as well as jQueryUI's version, some options and some private functions. For the tooltip, the name is "ui.tooltip".

Little example snippet below taken from the file jquery.ui.tooltip.js:

(function( $ ) {
  /**  Some functions here (redacted for easier reading).  **/
  $.widget( "ui.tooltip", {
    version: "1.10.4",
    options: {
      /**  List of options would be here (redacted for easier reading).  **/
    },
    /**  List of private functions (redacted for easier reading).  **/
  });
}( jQuery ) );

It might also be worth noting that this is the case in their latest development version located here (although there are some changes): https://github.com/jquery/jquery-ui/blob/master/ui/tooltip.js.

[thewebdreamer]

Nevermind, misread something for a moment there. They do directly inject into $. :(

[cvrebert]

Also, even if we wanted to do this, we couldn't do it until v4 due to backward-compatibility constraints.

[cvrebert]

@fat I assume that we're not gonna go this route? If so, then can we close as WontFix?

[fat]

yep wont fix