W3C home > Mailing lists > Public > www-style@w3.org > August 2012

Re: [whatwg] [selectors4] drag-and-drop pseudo-classes

From: Ryosuke Niwa <rniwa@webkit.org>
Date: Tue, 14 Aug 2012 13:11:19 -0700
Message-ID: <CABNRm61mhJpvYtwbfD7MpGP7oiRhSr222YN3yqxKt_q+4hc3=w@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: fantasai <fantasai.lists@inkedblade.net>, whatwg@lists.whatwg.org, "www-style@w3.org" <www-style@w3.org>, Daniel Cheng <dcheng@chromium.org>, Olli Pettay <Olli.Pettay@helsinki.fi>
On Tue, Aug 14, 2012 at 12:53 PM, Tab Atkins Jr. <jackalmage@gmail.com>wrote:

> On Tue, Aug 14, 2012 at 12:13 PM, Ryosuke Niwa <rniwa@webkit.org> wrote:
> > I'm asking how we're supposed to implement this pseudo-classes given that
> > the only way to know whether an element can receive the item is by firing
> > dragenter and/or dragover events. e.g.
>
> No, we can know it declaratively via the dropzone attribute.  That's
> what these will key off of in HTML.  In @dropzone, you can declare the
> types of data that it will accept, and you know the type of the data
> as soon as the drag starts, so you have all the info you need.
>

Okay, thanks for the clarification.

We obviously can't address "dropzones" that are only detectable during
> the dragover event.  That's fine - they just won't respond to these
> pseudo-classes.  Consider it an inducement to use the new, better
> model that @dropzone allows.
>

I'm not sure if I'm a big fun of that idea given that I haven't seen people
using dropzone attribute in wild. Have other browser vendors even
implemented it yet? (We haven't prefixed it in WebKit) All in all, I feel
like it's premature to build more features on top of it.

- Ryosuke
Received on Tuesday, 14 August 2012 20:12:06 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:58 GMT