Hi guys!

Sorry it took me so long to respond!

I've created my own test case according to your demo, and found out about a
couple of things.
First, there were issues you don't even know of, related to the placeholder
size in the new
trunk version, which I think I've fixed (in r804).

However, the issue that happens when the container's position is relative in
IE was something
really hard to debug.

1) It's not a bug in UI sortables
2) It's not a bug in jQuery
3) It's a bug in IE's getBoundingClientRect method, that is supposed to
return the offset, and is
    used by jQuery's offset method.

Here's the explanation: This bug only occurs if you have a positioned parent
element with exclusively
floating content in it, like we have here. Due to the floating nature of the
elements, they don't take
any size in the parent container, and without any size, IE reports very
strange positions.

The issue can be simply fixed by setting any height on the parent element,
even 1px!

Hope this helps!
Paul

On Fri, Oct 17, 2008 at 7:56 AM, tallvanilla <[EMAIL PROTECTED]> wrote:

>
>
> Thanks Olivier.
>
> Hey developers... any news on fixing this bug?
>
> Again, here's a live demo of the problem as it shows up in IE:
>
> http://74.205.76.81/sorttest/index4.php
>
> JR
>
>
>
> On Oct 16, 3:14 am, "Olivier Percebois-Garve" <[EMAIL PROTECTED]>
> wrote:
> > sure here it is.
> >
> > On my way I discovered another more subtle bug. I'm pretty sure it can be
> > reproduced on the photo gallery demo.
> >
> > change:
> >
> >         // make the trash box droppable, accepting images from the
> content section only
> >         $('#trash div').droppable({
> >                 accept: '.img_content',
> >                 activeClass: 'active',
> >                 drop: function(ev, ui) {
> >                         var $that = $(this);
> >                         ui.draggable.parent().fadeOut('slow', function()
> {
> >                                 ui.draggable
> >                                         .hide()
> >                                         .appendTo($that)
> >                                         .fadeIn('slow')
> >                                         .animate({
> >                                                 width: '72px',
> >                                                 height: '54px'
> >                                         })
> >                                         .removeClass('img_content')
> >                                         .addClass('img_trash');
> >                                 $(this).remove();
> >                         });
> >                 }
> >         });
> >
> > with:
> >
> >         // make the trash box droppable, accepting images from the
> content section only
> >         $('#trash div').droppable({
> >                 accept: '.img_content',
> >                 activeClass: 'active',
> >                 drop: function(ev, ui) {
> >                         var $that = $(this);
> >                         //ui.draggable.parent().fadeOut('slow',
> function() {
> >                                 ui.draggable
> >                                         .hide()
> >                                         .appendTo($that)
> >                                         .fadeIn('slow')
> >                                         .animate({
> >                                                 width: '72px',
> >                                                 height: '54px'
> >                                         })
> >                                         .removeClass('img_content')
> >                                         .addClass('img_trash');
> >                                 $(this).remove();
> >                         //});
> >                 }
> >         });
> >
> > That should trigger the bug. If not, ask me, I'll pprovide a zip.
> > I think that the current demo code works because the timer of the
> animation
> > allows the placeholder the be switched with the ui.draggable in time, so
> it
> > can be properly removed.
> > Without animation, the code breaks.
> >
> > Olivier
> >
> > On Wed, Oct 15, 2008 at 9:23 PM, tallvanilla <[EMAIL PROTECTED]>
> wrote:
> >
> > > Thanks Olivier. There's a fix described above that hasn't been
> > > released yet. Please try my demo page in FF and let me know if you
> > > still see the bug:
> >
> > >http://74.205.76.81/sorttest/index4.php
> >
> > > I only see it in IE, but I haven't tried YOUR demo yet, because I
> > > can't open a RAR file. Can you please provide a ZIP?
> >
> > > These kinds of bugs are show-stoppers, so I'm holding my breath until
> > > the "officials" weigh in on this!
> >
> > > JR
> >
> > > On Oct 15, 1:42 am, "Olivier Percebois-Garve" <[EMAIL PROTECTED]>
> > > wrote:
> > > > Hi tallvanilla
> >
> > > > I attached a demo of my bug.
> > > > It can be reproduced in FF, just make sure you scrolled down a
> little,
> > > and
> > > > then try dragging one of the blue boxes.
> >
> > > > Olivier
> >
> > > > On Wed, Oct 15, 2008 at 4:37 AM, tallvanilla <[EMAIL PROTECTED]>
> > > wrote:
> >
> > > > > UPDATE:
> >
> > > > > Another member of this group (Olivier Percebois-Garve) just found a
> > > > > NEW bug related to this one, so I thought I'd continue this
> discussion
> > > > > with his findings.
> >
> > > > > Please refer to one of my UI.SORTABLE demo pages for what was
> supposed
> > > > > to be the FIXED version of the bug discussed higher up on this
> page:
> >
> > > > >http://74.205.76.81/sorttest/index4.php
> >
> > > > > Unfortunately, it seems to exhibit a NEW bug, which Olivier
> > > > > discovered. To reproduce the bug (using IE only), just resize the
> > > > > browser window until a scrollbar appears. Then try dragging an
> element
> > > > > below the fold and back upwards. On the way up (and thereafter),
> > > > > you'll see a disconcerting distance between the mouse and the
> cloned
> > > > > element, very similar to what I reported earlier. You'll also
> notice
> > > > > that the greater the scroll length, the greater the distance
> between
> > > > > the mouse and the cloned element.
> >
> > > > > Another show-stopper! Please help again, Jeffrey Kretz and Paul
> > > > > Bakaus!
> >
> > > > > JR
> >
> > > > > On Oct 13, 4:55 pm, tallvanilla <[EMAIL PROTECTED]> wrote:
> > > > > > Thanks Paul. Will do! In the mean time, Jeffrey's fix (commenting
> out
> > > > > > line 41) seems to have done the trick.
> >
> > > > > > Also, I noticed that the currently nightly build does NOT include
> the
> > > > > > problematic line, so perhaps this bug fix is already underway?
> >
> > > > > > JR
> >
> > > > > > On Oct 13, 2:11 pm, "Paul Bakaus" <[EMAIL PROTECTED]>
> > > wrote:
> >
> > > > > > > Hey guys,
> >
> > > > > > > this definitely looks like a bug. Unfortunately, our bugtracker
> is
> > > down
> > > > > > > right now,
> > > > > > > but it should be up again in the next days.
> >
> > > > > > > Could you check again next weekend or so and then fill out a
> new
> > > bug
> > > > > report
> > > > > > > and attach a demo so we can track it down? That would help me a
> > > lot.
> >
> > > > > > > Thanks,
> > > > > > > Paul
> >
> > > > > > > On Mon, Oct 13, 2008 at 1:39 PM, tallvanilla <
> > > [EMAIL PROTECTED]>
> > > > > wrote:
> >
> > > > > > > > I see! I hate to mess with the actual plug-in, but you're
> > > right...
> > > > > > > > that fixed it too. Here's a version with your suggested
> > > modification
> > > > > > > > to ui.sortable.js:
> >
> > > > > > > >http://74.205.76.81/sorttest/index4.php
> >
> > > > > > > > I can't help but wonder if commenting out that line (line 41)
> > > will
> > > > > > > > have some undesirable side-effect at some point.
> >
> > > > > > > > Which leads me to this: Where are the UI developers? Why
> haven't
> > > they
> > > > > > > > chimed in by now? Isn't this the official forum for UI
> issues?
> > > I'm
> > > > > > > > hesitant to use (or advocate) any plug-in with a hands-off
> > > approach
> > > > > to
> > > > > > > > support and development, so I hope they weigh in on this
> > > eventually.
> > > > > > > > Meanwhile, thank you again JEFFREY for taking the time to
> > > identify
> > > > > and
> > > > > > > > solve this bug in their absence!
> >
> > > > > > > > JR
> >
> > > > > > > > On Oct 12, 4:51 pm, "Jeffrey Kretz" <[EMAIL PROTECTED]>
> > > wrote:
> > > > > > > > > Actually, I was more referring to a potential bug in the
> > > > > ui.sortable.js
> > > > > > > > > script.
> >
> > > > > > > > > When I commented out line 41, the behavior of the sortable
> > > acted
> > > > > the same
> > > > > > > > in
> > > > > > > > > IE7 and in FF (i.e. the position was correct).
> >
> > > > > > > > > You could try pulling down the nightly build and giving
> that a
> > > test
> > > > > run,
> > > > > > > > in
> > > > > > > > > case there are bugfixes that aren't yet released.
> >
> > > > > > > > > JK
> >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: [email protected] [mailto:
> > > > > [EMAIL PROTECTED] On
> >
> > > > > > > > > Behalf Of tallvanilla
> > > > > > > > > Sent: Sunday, October 12, 2008 4:08 PM
> > > > > > > > > To: jQuery UI
> > > > > > > > > Subject: [jquery-ui] Re: sortable: strange dragging
> behavior in
> > > IE
> > > > > ( demo
> > > > > > > > > included )
> >
> > > > > > > > > Thanks for taking the time, Jeffrey!
> >
> > > > > > > > > Picking up where you left off, I tried setting the
> containment
> > > > > element
> > > > > > > > > (id="sortboundary") to "position: fixed", but nothing
> changed:
> >
> > > > > > > > >    http://74.205.76.81/sorttest/index2.php
> >
> > > > > > > > > Maybe that isn't what you meant, so I tried setting the
> > > sortable
> > > > > > > > > items' parent DIV (id="boxes") to "position: fixed", and it
> > > worked!
> > > > > > > > > But only in IE(6?). It broke in every other browser:
> >
> > > > > > > > >    http://74.205.76.81/sorttest/index3.php
> >
> > > > > > > > > I'm thinking I can use the CSS underscore hack to set
> > > "_position:
> > > > > > > > > fixed" for IE6 only. Is this the best way to overcome the
> bug?
> >
> > > > > > > > > If so, my only remaining question is... does IE7 require
> the
> > > same
> > > > > fix
> > > > > > > > > as IE6? I don't have IE7 (don't want to install it over
> IE6),
> > > so I
> > > > > > > > > can't test this for myself. When you have a minute, can you
> > > please
> > > > > > > > > tell me if the following version works consistently across
> all
> > > > > > > > > relevant browers?:
> >
> > > > > > > > >    http://74.205.76.81/sorttest/index4.php
> >
> > > > > > > > > Thanks again for your time. I really appreciate it, and I
> think
> > > > > this
> > > > > > > > > is a vital issue for anyone using UI sortable!
> >
> > > > > > > > > JR
> >
> > > > > > > --
> > > > > > > Paul Bakaus
> > > > > > > UI Architect
> > > > > > > --http://paulbakaus.comhttp://www.linkedin.com/in/paulbakaus
> >
> > > >  jqueryui-draggables-bug.rar
> > > > 89KViewDownload
> >
> >
> >
> >  jqueryui-draggables-bug.zip
> > 93KViewDownload
> >
>


-- 
Paul Bakaus
UI Architect
--
http://paulbakaus.com
http://www.linkedin.com/in/paulbakaus

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"jQuery UI" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/jquery-ui?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to