(bump) Anybody? This is worth fixing. As much as we all hate it, IE is still the dominant web browser.
JR On Oct 17, 4:30 pm, tallvanilla <[EMAIL PROTECTED]> wrote: > Thanks Paul. This seems to have worked. I simply set the parent > element's height using [ style="height: 1px;" ], and IE started > playing nice: > > http://74.205.76.81/sorttest/index6.php > > In fact, setting the parent's height is now the ONLY difference > between the demo above, and the original problematic demo in this > thread: > > http://74.205.76.81/sorttest/index.php > > Furthermore, setting the parent's height works with the current > version of ui.sortables which does NOT have line 41 omitted. Is that > the expected behavior? Does line 41 stay after all? This fix doesn't > seem to work without it. > > ====== > > NEW ISSUE: > > When the scrollbar is present (in IE), auto-scrolling while dragging > only works in one direction at a time. For example, if you drag down, > the browser will scroll down, but it won't scroll back up if you drag > up - unless you drop the item first and start dragging again. The same > is true regardless of which direction you drag first (up or down). > Please see for yourself: > > http://74.205.76.81/sorttest/index6.php > > Any ideas? Good progress is being made so far! > > ====== > > Finally... the new bugs you found don't seem to be affecting my > current project, so I'm hesitant to download the updated plugin until > it's officially released. Is that likely to happen soon? > > JR > > On Oct 17, 10:21 am, "Olivier Percebois-Garve" <[EMAIL PROTECTED]> > wrote: > > > Thanks Paul. > > > It worked and your fix solved the drag & drop bug in a absolute positioned > > container. > > > thanks a lot > > > keep up the good work > > > Olivier > > > On Fri, Oct 17, 2008 at 3:17 PM, Paul Bakaus <[EMAIL PROTECTED]>wrote: > > > > if you want a complete file, there's a build script in /trunk/release/ > > > > you have to grab Ant for Windows, and then go to that folder via > > > command line, and execute "ant deploy-release". That will generate > > > a new build. > > > > On Fri, Oct 17, 2008 at 3:13 PM, Olivier Percebois-Garve < > > > [EMAIL PROTECTED]> wrote: > > > >> Thanks a lot Paul, > > > >> How to use the last svn version ? > > >> I have downloaded the repository, but it is separated into several > > >> files. > > >> What do have I to do build jquery-ui from that ? > > > >> Olivier > > > >> On Fri, Oct 17, 2008 at 10:49 AM, Paul Bakaus <[EMAIL PROTECTED] > > >> > wrote: > > > >>> 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: > > ... > > read more ยป --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
