> I have posted a fix in lighthouse for this bug:
> https://mootools.lighthouseapp.com/projects/2706/tickets/662-patch-to-enable-fixed-position-droppables-for-dragmove
I am not sure if this is applicable - the element in question is not
of "fixed" position, there is no scroll to speak of in my resolution and
the check takes place through getPosition instead of getCoordinates.
the draggable icon is a static/relative position element that is a child
of a position: static /relative element that sits in a number of nested
elements similar elements, ultimately children of the modal box, with
absolute position.
the problem takes place as soon as the draggable el swaps to being
absolute - and then assumes the position of its parent modalBox, which
is also absolute.
as soon as you start dragging it, since it has a [container], it gets
sent to the container boundaries' topLeft by the Drag class.
I hope this makes sense... As a fix, I tried reading the coordinates of
the element before applying the drag on it and then repositioning it
again:
// relative to the modalBox seems to work...
var coords = this.mover.object.getPosition($("mOOdalBox"));
this.drag = this.mover.object.makeDraggable({
droppables: [this.dropper],
container: this.container,
....
});
if (Browser.Engine.trident)
this.mover.object.setPosition({
x: coords.x,
y: coords.y + 4
});
which is ok for for my needs - but I will disable the workaround for now
so that the bug remains visible....
Regards,
--
[email protected] | http://fragged.org/
