#3 new
AMA3

Sortable.create drops draggable despite option.only; onUpdate (correctly) not called

Reported by AMA3 | May 10th, 2008 @ 12:48 AM

h1.SCENARIO

I have two types of Sortables that share Draggables (by containment):

  1. a "groupDrop" can contain only Draggable "field" elements.
  2. a "zone" can contain Draggable "field" elements and/or Draggable "group" elements.

A Sortable "groupDrop" is always within a Draggable "group".

Each "groupDrop" has option only:"field" to prevent one group from being dropped within another.

h1.PROBLEM:

If a "group" is dragged from a "zone" and dropped in a "groupDrop", the groupDrop correctly does not invoke the onUpdate function. However, the group incorrectly drops in the groupDrop, and the zone onUpdate function is invoked (and missing the dragged group).

h1.DESIRED RESOLUTION:

If a "groupDrop" is set to only accept a "field", then any attempt to drop a "group" in it should fail completely. The "group" should revert back to its original position.

[Note: this was trac ticket #11621]

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

script.aculo.us is an open-source JavaScript framework for visual effects and interface behaviours.
<br/><b>Source available from github</b>
The Git repository resides at:
<a href="http://github.com/madrobby/scriptaculous">http://github.com/madrobby/scriptaculous</a>
<br/>Check out the current development trunk with:
<code>git clone git://github.com/madrobby/scriptaculous.git</code>
<br/>As <b>script.aculo.us 1.xx is feature-frozen</b>, this development trunk is for <b>bugfixes only</b>.
<br/>New development should happen only for
<b>script.aculo.us 2</b>.
<br/><b>Creating a bug report</b>
When creating a bug report, be sure to include as much relevant information as possible. Post a an example that shows off the problem. Preferably, <b>alter the unit tests</b> and show through either changed or added tests how the expected behavior is not occuring.

People watching this ticket

Attachments

Pages