Sortables within overflow div - part2
Ralph Slooten
I wrote about this issue I was having several months back, and was told
it was fixed in the 1.2.2 release. The truth was it didn't make any
difference to the issues I was having with IE, and as on version 1.2.3 I
now have this same issue with Firefox (all versions) too.
I thought it best to set up a demo to better explain the issue:
http://www.axllent.org/mtdrag/
What you will notice is that for both 1.2.2 and 1.2.3 of the mootools
versions (you can select which from the drop-down), the first couple of
rows of images can be dragged & reordered without an issue on both IE
and FF, provided you do not scroll down.
With 1.2.3 on both IE and FF, and 1.2.2 on IE, scrolling down causes a
negative (upwards) offset of the ghost image, and a positive (downwards)
offset of the actual dragged image ~ and re-ordering becomes impossible
once the offset "disappears" out of the div's borders.
I need to do this in an overflow div, so my questions are:
a) Is there another way that I'm now aware of to achieve the same thing, or
b) Is there a potential fix
Any helps would be greatly appreciated.
With kind regards,
Ralph
nutron
View this message in context: Re: [Moo] Sortables within overflow div - part2
Sent from the MooTools Users mailing list archive at Nabble.com.
Ralph Slooten
Thanks.
nutron wrote:
> Ralph can you open a lighthouse ticket for this:
>
> http://mootools.lighthouseapp.com/projects/24057-mootoolsmore/
>
> On Wed, Jul 1, 2009 at 7:40 PM, Ralph Slooten (via Nabble)
> <ml-user%2B199636-292879764@...
> The MooTools Tutorial: www.mootorial.com <http://www.mootorial.com>
> Clientcide: www.clientcide.com <http://www.clientcide.com>
>
> ------------------------------------------------------------------------
> View this message in context: Re: [Moo] Sortables within overflow div -
> part2
> <http://n2.nabble.com/-Moo--Sortables-within-overflow-div---part2-tp3193069p3197734.html>
> Sent from the MooTools Users mailing list archive
> <http://n2.nabble.com/MooTools-Users-f660466.html> at Nabble.com.
nutron
Sent from the MooTools Users mailing list archive at Nabble.com.
Ralph Slooten
> I'll try and look into it soon.
Thank you, it would be greatly appreciated!
ankit
onwieze
And it looks like this is a shared problem with the Fx.Scroll class.
Because when I say scrollTo(element) it does it completely wrong for
element when I am not scrolled to the top.
So both classes probably share some logics about the location, i
think.
kasi
KASI
anutron
I also have this problem.
And it looks like this is a shared problem with the Fx.Scroll class.
Because when I say scrollTo(element) it does it completely wrong for
element when I am not scrolled to the top.
So both classes probably share some logics about the location, i
think.
On 3 jul, 21:38, ankit <ahuja.an...@...> wrote:
> +1, I'm having the same problem.
>
> On Jul 3, 3:32 am, Ralph Slooten <axll...@...> wrote:
>
> > nutron wrote:
> > > I'll try and look into it soon.
>
> > Thank you, it would be greatly appreciated!
Ralph Slooten
> Giving the galeryHolder div the style position:relative fixes it.
Adding position:relative to #galleryHolder doesn't make the slightest
bit of difference here with FireFox 3.5, and totally breaks the overflow
with IE8 :-/
kasi
position.
Next problem is in Drag.Move when checking against dropables , the
dropables do not respect the scrolling.
And last in IE when dragging image the option preventDefault must be
set to true (Drag.Move).
Look at:
http://kasi-hamburg.de/mootools/moohelp/sortables/sortables.htm
works with IE8, Opera 9.64 and FF 3.0.11
Hope this brings some light into the problem.
KASI
Ralph Slooten
This solution works great (tested with FF 3.5, IE 6 & 8, Opera 9.6,
Safari 4 & the latest Chrome).
Now, from what I can see, all you have actually done here to correct the
is main issue was to extend the Drag.Move class by adding scroll offsets
to the current drag position,am I correct? On top of that issue there
are two others related (preventDefault option and relative position).
If this is the case, the fix in MooTools should be rather simple, also
correct?
Thanks for taking the time to look into this! Aaron, does this give you
guys some direction as to what the problem is and a possible fix? If so,
and I understand the solution correctly, shall I copy/paste the previous
email from Kasi into Lighthouse?
Cheers,
Ralph