- From: Daniel Cheng <dcheng@chromium.org>
- Date: Fri, 30 Sep 2011 13:24:18 -0700
That's fine. The reason it works that way is inside the dragstart handler, when you call setDragImage, we merely retain a reference to the element you passed in. We don't actually create the drag image until after dragstart processing is finished. As I read it though, setDragImage() is supposed to snapshot the element at the time the method is called. Daniel On Fri, Sep 30, 2011 at 13:13, Rafa? Mi?ecki <zajec5 at gmail.com> wrote: > W dniu 30 wrze?nia 2011 19:44 u?ytkownik Daniel Cheng > <dcheng at chromium.org> napisa?: > > Please file a bug for WebKit at https://bugs.webkit.org and attach your > test > > case there (I do not see it on your email). > > Please take a look at: > https://bugs.webkit.org/show_bug.cgi?id=69165 > > I was afraid attachment can be stopped by the mailing list, that's why > I sent (without success) attachment in the second mail. Now you can > see test case using Webkit's bugzilla: > https://bug-69165-attachments.webkit.org/attachment.cgi?id=109335 > > Seeing the same behavior in Webkit and Gecko made me thinking if this > is really a bug. Or my misinterpretation of specs. That's why I > decided to post this e-mail before reporting bug. > > P.S. > Daniel: I hope you don't mind I responded to you *and list*. > > -- > Rafa? >
Received on Friday, 30 September 2011 13:24:18 UTC