W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2012

Re: [whatwg] Proposed addition to Drag and Drop API

From: Alex Bain <alex@alexba.in>
Date: Fri, 29 Jun 2012 16:37:44 -0700
To: Daniel Cheng <dcheng@chromium.org>
Message-ID: <BE997CF2DBB84E6E87CDFADC8FE38317@alexba.in>
Cc: whatwg@lists.whatwg.org, Ryosuke Niwa <rniwa@webkit.org>, Tony Chang <tony@chromium.org>
@Ryosuke - I do not have a concrete proposal but would be interested in helping to work one out. I had idly considered a content attribute but think that specifying an element (perhaps via a function called setDragElement()) would be a simple implementation.

@Daniel - I had thought that was possible but in my testing I was not able to get it to work. I had tried referencing an existing element as well as creating a new element but neither were visible while dragging [in Chrome].

On Friday, June 29, 2012 at 4:30 PM, Daniel Cheng wrote:

> Can't you use setDragImage() and pass it the element that holds the post title?
> Daniel 
> On Fri, Jun 29, 2012 at 4:27 PM, Ryosuke Niwa <rniwa@webkit.org (mailto:rniwa@webkit.org)> wrote:
> > On Fri, Jun 29, 2012 at 4:24 PM, Alex Bain <alex@alexba.in (mailto:alex@alexba.in)> wrote:
> > > I would prefer not to visually drag the entire post around (which is what happens if I set draggable to true on the post container). My goal is to set draggable on a container element and only show a small element when the user starts dragging.
> > 
> > Ah, that's an interesting use case. Thanks for clarification. Do you have a concrete proposal for this? (e.g. adding new content attribute / element).
> > 
> > - Ryosuke 
> > 
Received on Friday, 29 June 2012 23:38:12 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:14 UTC