On Aug 14, 2012 10:54 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Tue, Aug 14, 2012 at 12:13 PM, Ryosuke Niwa rn...@webkit.org wrote:
Yeah, and that's not compatible with how drag and drop are implemented
on
the Web.
I know. You'll notice that I didn't suggest we somehow change to
On Wed, Aug 15, 2012 at 9:12 AM, Henri Sivonen hsivo...@iki.fi wrote:
On Aug 14, 2012 10:54 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Tue, Aug 14, 2012 at 12:13 PM, Ryosuke Niwa rn...@webkit.org wrote:
Yeah, and that's not compatible with how drag and drop are implemented
on
the Web.
The CSSWG discussed drag-and-drop pseudo-classes today. The current
proposal is to have three pseudo-classes:
* One for the element representing the drop target that
would receive the item if it were dropped.
* One for all elements representing possible drop targets
that could
On Mon, Aug 13, 2012 at 9:19 PM, fantasai fantasai.li...@inkedblade.netwrote:
The CSSWG discussed drag-and-drop pseudo-classes today. The current
proposal is to have three pseudo-classes:
* One for the element representing the drop target that
would receive the item if it were dropped.
On Mon, Aug 13, 2012 at 11:55 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Mon, Aug 13, 2012 at 9:19 PM, fantasai
fantasai.li...@inkedblade.netwrote:
The CSSWG discussed drag-and-drop pseudo-classes today. The current
proposal is to have three pseudo-classes:
* One for the element
On Tue, Aug 14, 2012 at 3:03 AM, Sebastian Zartner
sebastianzart...@gmail.com wrote:
* One for all elements representing possible drop targets
that could receive the item.
* One for all elements representing drop targets that do
not accept this type of item.
This sounds like
On 08/13/2012 11:55 PM, Ryosuke Niwa wrote:
On Mon, Aug 13, 2012 at 9:19 PM, fantasai fantasai.li...@inkedblade.net
mailto:fantasai.li...@inkedblade.net wrote:
The CSSWG discussed drag-and-drop pseudo-classes today. The current
proposal is to have three pseudo-classes:
* One
On 08/14/2012 03:03 AM, Sebastian Zartner wrote:
* One for all elements representing possible drop targets
that could receive the item.
* One for all elements representing drop targets that do
not accept this type of item.
This sounds like these two
On Tue, Aug 14, 2012 at 11:04 AM, Tab Atkins Jr. jackalm...@gmail.comwrote:
On Mon, Aug 13, 2012 at 11:55 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Mon, Aug 13, 2012 at 9:19 PM, fantasai fantasai.li...@inkedblade.net
wrote:
The CSSWG discussed drag-and-drop pseudo-classes today. The
On Tue, Aug 14, 2012 at 12:13 PM, Ryosuke Niwa rn...@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
On Tue, Aug 14, 2012 at 12:53 PM, Tab Atkins Jr. jackalm...@gmail.comwrote:
On Tue, Aug 14, 2012 at 12:13 PM, Ryosuke Niwa rn...@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
11 matches
Mail list logo
