[Webkit-unassigned] [Bug 114643] WebKit does not expose HTML5 drag/drop status

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Feb 26 10:03:35 PST 2015


https://bugs.webkit.org/show_bug.cgi?id=114643

Don <donshreds at yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |donshreds at yahoo.com

--- Comment #6 from Don <donshreds at yahoo.com> ---
Hi Pranav,

Its possible to at least get the drag and drop aspect of the demo working by changing the background-image urls.

I grabbed a copy of the testcase, and edited it just now to use a different URL. I changed the title lines in the style section as follows, pointing to a Google image instead of the twitter images. With this change, at least now you can visually see something (corner of the Google logo) that's draggable.

[title="remy"]        { background-image: url(https://www.google.com/images/srpr/logo11w.png); }
[title="brucel"]      { background-image: url(https://www.google.com/images/srpr/logo11w.png); }
[title="Rich_Clark"]  { background-image: url(https://www.google.com/images/srpr/logo11w.png); }
[title="leads"]       { background-image: url(https://www.google.com/images/srpr/logo11w.png); }
[title="akamike"]     { background-image: url(https://www.google.com/images/srpr/logo11w.png); }
[title="jackosborne"] { background-image: url(https://www.google.com/images/srpr/logo11w.png); }

In fact, even prior to this change, I could still get drag and drop aspect of the demo to work in Firefox and Safari, just by mousing over where the images would show up if the url's were valid I found the elements are still there...just because the URL is invalid and the browser cannot render/show the image, doesn't mean there still isn't a draggable <li> element there, its just not visible is all. Anyway, the above makes it a little easier to spot the images.

Per Chris's append on 02-23, and reading between the lines a bit:

My guess what needs to happen here is that the existing webkit methods (that Chris mentions) that expose draggable information, are only looking at webkit-specific properties like -webkit-user-drag. We need to modify those methods (Chris, please feel free to correct me if I am wrong) to *additionally* look at the new HTML-5 attributes (such as 'draggable'), and effectively treat those the same way as the original equivalent webkit properties

Does that sound about right to you Chris?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150226/31566236/attachment-0002.html>


More information about the webkit-unassigned mailing list