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

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

From: Marat Tanalin | tanalin.com <mtanalin@yandex.ru>
Date: Wed, 15 Aug 2012 02:01:21 +0400
To: fantasai <fantasai.lists@inkedblade.net>
Cc: "www-style@w3.org" <www-style@w3.org>,"whatwg@lists.whatwg.org" <whatwg@lists.whatwg.org>
Message-Id: <1260801344981681@web3g.yandex.ru>
14.08.2012, 08:19, "fantasai" <fantasai.lists@inkedblade.net>:
> šššb) what these pseudo-elements should be called, that would best
> šššššš(most clearly and succinctly) represent their functionality
> ššššššto authors using them
> Name sets being considered:
> šššššSet A ššššššššSet B ššššššSet C šššššššššššSet D
> ----------------------------------------------------------------
> šš:active-drop ššš:drop ššššššš:current-drop ššš:active-drop
> šš:drop šššššššššš:can-drop ššš:valid-drop ššššš:valid-drop
> šš:no-drop ššššššš:no-drop šššš:invalid-drop ššš:invalid-drop

>From these options, set B seems to be most intuitive for me.

Though, it may make sense to use more specific `:drop-target` name instead of just `:drop` for first of pseudoclasses. Also, `:cannot-drop` maybe is more consistent with `:can-drop` and thus more suitable than `no-drop` (when using in same set as `:can-drop`). Also, `drop` may be used as a prefix (be at the beginning of pseudoclass name) for the all three. Alternatively, `valid`/`invalid` instead of `can`/`cannot` could be fine too. Sothat we'd end up with one of following two sets:

     Set MT1         Set MT2
    :drop-target    :drop-target
    :drop-can       :drop-valid
    :drop-cannot    :drop-invalid
Received on Tuesday, 14 August 2012 22:02:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:20 UTC