#133 new
nrajlich

position:fixed Droppable accepts draggables as if it were absolute (considers scroll offset)

Reported by nrajlich | December 7th, 2008 @ 04:08 AM

If there's a Droppable on the page, and it's element has a position set to "fixed", and there is a scroll offset in the droppable's container, then it will behave incorrectly.

It will behave correctly when there is no scroll offset (scrolled all the way to the top), but when the user scrolls down, the position of the draggable scrolls with the page, but the element of the draggable is fixed on the page (like it should be).

This was tested using the latest versions of both Prototype and Scriptaculous.

I've attached a demonstration of this in action. I'll look into it a bit further myself, but I would definitely consider this a bug, and hopefully somebody out there will be able to come up with a fix.

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