FLUID-1616: The function "selectable" clashes with jQuery UI ui.selectable.js

Description

We need to change our API for the plugin so that people can use the pluggin on a page that also imports ui.selectable.js

This bug cropped up when integrating with uPortal

Attachments

• FLUID-1616-uportal-patch.txt

Comments

• Anastasia Cheetham commented 2008-09-25T14:27:34.000-0400

  I'm giving this patch to Jen Bourey to see if it addresses the problems she's having integrating the LayoutReorderer into uPortal.

• Michelle D'Souza commented 2008-10-01T13:48:17.000-0400

  dev-iteration45
  dev-iteration46

• Anastasia Cheetham commented 2008-11-05T16:48:40.000-0500

  The patch did work for Jen, though they ended up not using it. Instead, they removed the selectables component from the uPortal import
  list since they weren't using it.

• Justin Obara commented 2008-12-03T12:20:54.000-0500

  Bug Parade 0.6 release

• Antranig Basman commented 2008-12-09T15:16:22.000-0500

  This has been resolved in a comprehensive manner as of revision 6181 with a new approach based on generalised "bridging" of the standard Fluid "that-ist" semantics to the JQuery UI standard "this-ist + chaining" model. In this way the entire Fluid framework, which has appropriate signatures, is available as a single JQuery UI plugin "fluid", and likewise, the former contents of keyboard-a11y.js are now available to Fluid code via standard fluid.function(args) syntax.
  This moves all of this plugin code permanently out of harm's way in terms of future namespace collisions with the rest of the JQuery community, whilst preserving its modularity and also improving its conformance to the JQuery UI plugin guidelines. Documentation to follow - all samples and test cases updated.

• Michelle D'Souza commented 2008-12-12T12:22:53.000-0500

  I reviewed the code changes and it looks good. Having fluid available through jQuery UI style invocation should make for easier uptake by the jQuery community.

• Justin Obara commented 2008-12-12T13:45:56.000-0500

  Verified fix using:

  FF3, FF2 (Mac OS 10.5)

  FF3, IE7 (Win Vista)