Re: function Element.isParent argument order?

azaozz
Mon, 25 Jun 2007 07:07:48 -0000

Hi Gareth, no, the zero margins work fine. I had another "jumpy"
problem with a Droppable, where the Sortables had to be expanded and
wrapped around on several lines. The first line was OK but the second,
third, etc. were still jumpy in IE6. In a few days I''ll put up a demo
web page and you''ll be able to see it exactly.

Switching the arguments for Element.isParent fixed the jumpiness in
IE, but made the dragging speed slower. Then I noticed that if there
is some kind of output to the browser while dragging, the speed in IE6
is the same as in FF and Opera.

On Jun 24, 9:02 pm, "Gareth Evans"
<agr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> Is this another fix required as well as the margin thing to get it to work
> smoothly azaozz?
>
> Gareth
>
> On 6/25/07, azaozz <aza...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
>
>
>
> > I was trying to troubleshoot "jumpy" Sortables and noticed
that when
> > the function Element.isParent is called from onHover (line 749 in
> > dragdrop.js v. 1.7.1_beta3) and from onEmptyHover (line 781), the
> > arguments seem to be in reverse order.
>
> > Element.isParent (line 944) expects "child, element(parent)"
but is
> > called with "dropon(parent), element(child)", making it
return FALSE
> > most of the time, when (I think) it should be returning TRUE...
>
> > Reversing the arguments order on lines 749 and 781 to
> > "Element.isParent(element, dropon)" fixes any
"jumpiness" in
> > horizontally arranged Sortables when they overflow on more than 1 line
> > ( I use about 60 small ones - 20x20px and they overflow on 4-5 lines).