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:24:49 -0700
To: Ryosuke Niwa <rniwa@webkit.org>
Message-ID: <E6971CEF6FE84DB3AEDCE9D33D2ADF3A@alexba.in>
Cc: whatwg@lists.whatwg.org
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.

On Friday, June 29, 2012 at 4:21 PM, Ryosuke Niwa wrote:

> On Fri, Jun 29, 2012 at 4:12 PM, Alex Bain <alex@alexba.in (mailto:alex@alexba.in)> wrote:
> > I've spent the past few days working with the Drag and Drop API and I'd like to propose an addition to the spec to aid developers and designers in creating accessible drag interfaces.
> > 
> > **Use case:**
> > 
> > I'm developing an app that allows users to drag pieces of user generated content (Posts) from one part of the app to another. A Post is represented as a DOM subtree with multiple components - a title, some images, text, and so forth. I wanted to create an interaction where the user could click and drag anywhere on the Post (large click target for accessibility purposes), see a subset of the Post as a drag indicator (the title, for example), and then be able to drop that elsewhere in the app.
> You can't use draggable content attribute?
> http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html#the-draggable-attribute
> - Ryosuke
Received on Friday, 29 June 2012 23:25:18 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:43 UTC