On Thu, 30 Aug 2012, Trevor Burnham wrote:
The main use case I have in mind is an interface where elements respond
to the object being dragged. A common case is showing visual feedback
depending on whether the element emitting a dragenter/dragover is a
valid drop target for the object
On Thu, 21 Jun 2012, Trevor Burnham wrote:
I've been using HTML drag-and-drop
(http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html)
in a project, but I've run into one limitation that seems severe to me:
There is no direct way to determine what the source node is from a
On 30.8.2012 19:27, Ian Hickson wrote:
On Thu, 21 Jun 2012, Trevor Burnham wrote:
Therefore, I'd like to propose the addition of a publicData object on
all drag events. It would have the same interface and behavior as the
dataTransfer object, with the sole exception that it would be read-only
On Aug 30, 2012, at 1:27 PM, Ian Hickson i...@hixie.ch wrote:
On Thu, 21 Jun 2012, Trevor Burnham wrote:
I've been using HTML drag-and-drop
(http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html)
in a project, but I've run into one limitation that seems severe to me:
I've been using HTML drag-and-drop
(http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html) in a
project, but I've run into one limitation that seems severe to me: There is no
direct way to determine what the source node is from a dragenter, dragover, or
dragleave event. This
