Closed GoogleCodeExporter closed 9 years ago
I don't see that at all (in any version of IE on XP).
I assume you are dragging the image with a pointing device (though it shouldn't
matter if you use the keyboard as well). (?)
The DnD code is basically the same as it was when the library was released
(save for a couple of fixed typos that wouldn't affect the presentation of the
dragged element). It's been tested on IE9/Windows 7 as well (and lots of
non-IE browsers). I've never seen any browser make the dragged element
disappear as you describe. Though I suppose if you add a z-index style to the
drop target, you could make it obscure the dragged element.
Any additional information you can provide would be helpful.
Original comment by dmark.ci...@gmail.com
on 10 Dec 2010 at 6:44
Original comment by dmark.ci...@gmail.com
on 10 Dec 2010 at 6:45
i don't understand i can't reproduce it anymore
IE8 and maxthon 2 (IE8) were affected the 04/12
you didn't change anything since then?
Original comment by fun...@gmail.com
on 10 Dec 2010 at 7:10
Haven't touched it since then. Hadn't even looked at that example in years. :)
I do notice that due to odd padding styling in IE, part of the drop target area
is transparent, which makes the DnD example look pretty sloppy. I'll fix that
when I have a chance.
As for your issue, perhaps IE was in the middle of some sort of meltdown on
that machine.
Thanks for the report anyway. Better safe than sorry!
Original comment by dmark.ci...@gmail.com
on 10 Dec 2010 at 7:22
hope that was on my end (probably not)
if i had to guess though id say it was an opacity bug
or maybe the bug is revealed only in specific cases (you have to do something
before)
Original comment by fun...@gmail.com
on 10 Dec 2010 at 7:38
As for an opacity bug, it seems unlikely as the "ghost" effect when dragging is
purely CSS (and unrelated to dragging over or dropping on a target).
I considered what else on that test page could affect the z-index (or any)
style of the drop target (fieldset). It's been a while since I've thought
about that page and nothing comes to mind. I'd ask if you were in
compatibility mode, but I know that has no negative effect on those (or any)
tests.
All I can figure is that it was a momentary lapse in rendering for that
particular IE8.
Thanks again!
Original comment by dmark.ci...@gmail.com
on 10 Dec 2010 at 8:22
Original issue reported on code.google.com by
fun...@gmail.com
on 4 Dec 2010 at 7:22