#298 new

Bug on dragdrop.js (scrollable page/ div)

Reported by drow | August 11th, 2010 @ 02:58 PM

  1. Issue according scrollable pages/ div tags
    There is a problem according scrollable pages and the drapdrop detection. The value of scrollTop is just ignored in the respective method (using Position.within). Instead it should use Position.withinIncludingScrolloffsets, that fixes this issue. This issue was not tested on a scrollable page (but as the code excludes scrolling completely it should'nt work there as well).

  2. Issues according scroll option for Draggables
    When using the scroll option on Draggables inside a scrollable div, the position of the dragged element is not updated and therefore moves away from mouse pointer. Same problem occurs when the div tag is scrolled and starting to drag an element (position is not beyond mouse pointer). I wrote Thomas Fuchs an email today according that and a feature request (hook inside draw method) to solve this problem (see attached eml file).

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