Hi.
I've spended a lot of time on this strange behaviour :
here is the situation :
<body>
<div id="container1">
<div id="drag1"
class="draggable">drag1</div>
</div>
<div id="droppable">
Drop here <br />
</div>
</body>
drag1 is draggable with ghosting (without it there is no
problem)
and I set (via CSS) the container to be
"position:fixed".
At the end of a dragging, the drag1 go on a bad position (I
have track
the thing in Firebug and it seems to be when scriptaculous
try to do :
Position.relativize(this.element); in Draggable.finishDrag)
And because of that it sometimes misses the Droppable :
the test if (this.isAffected([Event.pointerX(event),
Event.pointerY(event)], element, this.last_active))
in Droppable.fire might indeed be false because of the bad
positionning.
At first I was experimenting that with a draggable with
ghosting and
revert, and because of the revert, I never saw the bad
positionning
but only the miss of the droppable, not easy at all to
understand...
I'm not sure if this is very understandable, but if someone
want to
try it, here it is :
h
ttp://arthur.petry.free.fr/test_js/test_fixed.html
(drag2 without ghosting has no problem, but drag1 is very
strange...)
I'm using scriptaculous 1.7.0, with Firefox 2.0.0.3 and
Safari 2.0.4.
--
Arthur
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribegooglegroups.com
For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=
en
-~----------~----~----~----~------~----~------~--~---
|
