Skip to main content

Search and Top Navigation

#4168 closed bug (wontfix)

Opened February 17, 2009 02:15PM UTC

Closed April 16, 2013 08:21PM UTC

Event name collision with mootools

Reported by: ntoniazzi Owned by:
Priority: major Milestone: 1.11.0
Component: ui.slider Version: 1.6rc6
Keywords: Cc:
Blocked by: Blocking:

When integrating jquery+ui (in noConflict mode) with mootools (not a choice), both libraries answer to the "slide" event, and unfortunately, mootools shoots first.

  • Mootools: Fx.Slide, "slide" method
  • jQuery-ui: ui.slider, "slide" callback

Shouldn't namespaced events prevent this kind of collision? By adding 'ui' or 'jquery-ui' somewhere?

Attachments (0)
Change History (9)

Changed March 08, 2009 02:30PM UTC by rdworth comment:1

milestone: 1.71.8

Changed March 25, 2009 05:18AM UTC by kungfu71186 comment:2

anyway to fix this?

Changed March 25, 2009 10:17AM UTC by ntoniazzi comment:3

A workaround is to remove any previous "slide" method before calling the plugin :


But it's only a workaround.

Changed November 30, 2010 06:57AM UTC by amsys comment:4

confirming this problem, the workaround resolved the issue for me, thanks

Changed July 21, 2011 03:03PM UTC by dostrog comment:5

Until ticket is opened, I've change name 'slide' in lib. Some details in my answer on stackoverflow:

It's work on my joomla 1.6 based site with mootools and jquery-ui enabled

Changed January 03, 2012 05:54PM UTC by cameronbot comment:6

The workaround in commet 3 by ntoniazzi did not work for me, however I found this answer on stackoverflow with another workaround which worked:

jQuery('div.slider')[0].slide = null;

Changed October 11, 2012 02:53PM UTC by scottgonzalez comment:7


Changed October 15, 2012 07:27PM UTC by tj.vantoll comment:8

status: newopen

We are planning on switching to firing "widget:event" (for example "slider.slide") to avoid naming collisions with native events.

In the meantime you can switch the prefix the slider plugin uses as a workaround -

Changed April 16, 2013 08:21PM UTC by scottgonzalez comment:9

resolution: → wontfix
status: openclosed

I'm not sure what Mootools is doing, or if this is still a problem, but I'm guessing that this falls into the Object.prototype-ish bucket.