#280 new

Dragging between fixed and non-fixed Sortables (position offset bugs)

Reported by io | April 4th, 2010 @ 04:03 PM


I have drag-snap-offset problems when dragging between Sortables.

My application involves dragging people from the 'available employees
list', on the right, to projects the person has applied for.
(unavailable targets are dimmed on drag start.)

Have a look at it here:

-> http://www.qasmartbr.nine.ch/unico/smartbridge/hr/indexgrp.php?acti....

username: gg password: gg

There seem to be 2 positioning bugs:

1) scrolling the main window causes weird offsets between the dragged
item and the snap-location in droppables.
2) scrolling within the 'available employee list' (when many employees
available) causes a similar problem.

Things work well only if when both of these are scrolled all the way

Note that the 'available employee list' has position:fixed and is
draggable itself (grab at top) !

So far, I have tried dragdropextra.js and many other patches and workarounds i found in the forums, without success :(


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