Re: [Clipboard] Processing model feedback (and other)

On Mon, Feb 20, 2012 at 2:30 AM, Hallvord R. M. Steen wrote: > ..but what about the steps we need to do for "copy" and "cut" events *if* > the canceled flag is set? It's actually a bit more complicated than "abort > these steps", which is why I'm not sure how I should structure it if I try > to fo

Re: [Clipboard] Processing model feedback (and other)

On Mon, 20 Feb 2012 00:09:56 +0100, Glenn Maynard wrote: You can use the wording I gave above (modified here slightly): 7. Fire an event using the *ClipboardEvent* interface, with its *type* attribute initialized to *e* and its *clipboardData* attribute initialized to *data transfer*, at *even

Re: [Clipboard] Processing model feedback (and other)

On Sat, Feb 18, 2012 at 10:12 AM, Hallvord R. M. Steen wrote: > I've looked at rewriting it but I'm not sure how. Cancelling the default > action has different outcomes for the different types of events. Some of > the outcomes are also easier to understand if you think that the default > action *i

Re: [Clipboard] Processing model feedback (and other)

Siterer Anne van Kesteren : Except there's no such thing as default action really... IMO this is well established terminology and easy to understand for script authors because of the preventDefault() method name.. I've changed the text slightly though. I don't really think the term is

Re: [Clipboard] Processing model feedback (and other)

Le 19 févr. 2012 à 10:46, Anne van Kesteren a écrit : > On Sat, 18 Feb 2012 16:45:07 +0100, Hallvord R. M. Steen > wrote: "Firing an event" surely should be specified elaborately elsewhere. I added another reference to DOM2-Events (though "fire" probably is used without being p

Re: [Clipboard] Processing model feedback (and other)

On Sat, 18 Feb 2012 16:45:07 +0100, Hallvord R. M. Steen wrote: "Firing an event" surely should be specified elaborately elsewhere. I added another reference to DOM2-Events (though "fire" probably is used without being precisely spec'ed there..). Yes, you need to reference DOM4. Otherwise

Re: [Clipboard] Processing model feedback (and other)

On Thu, 16 Feb 2012 17:05:23 +0100, Glenn Maynard wrote: * The "Process the default action" step should instead talk about whether or not the http://dvcs.w3.org/hg/domcore/**raw-file/tip/Overview.html#** canceled-flagof

Re: [Clipboard] Processing model feedback (and other)

On Thu, 16 Feb 2012 14:35:50 +0100, Anne van Kesteren wrote: The processing model is about how to deal with a "copy/paste/cut operation" it is not about firing an event (that is mainly part of it). ..it happens to be *the* part of the processing this spec is all about :)..? I mean that

Re: [Clipboard] Processing model feedback (and other)

On Thu, Feb 9, 2012 at 7:20 AM, Hallvord R. M. Steen wrote: > * The "Process the default action" step should instead talk about whether >> or not the http://dvcs.w3.org/hg/domcore/**raw-file/tip/Overview.html#** >> canceled-flag

Re: [Clipboard] Processing model feedback (and other)

On Thu, 09 Feb 2012 14:20:57 +0100, Hallvord R. M. Steen wrote: Anne van Kesteren skreiv Fri, 09 Sep 2011 16:48:36 +0200 As a high-level comment it seems to me the organization of the specification needs some changing. The processing model is about how to deal with a "copy/paste/cut opera

Re: [Clipboard] Processing model feedback (and other)

Anne van Kesteren skreiv Fri, 09 Sep 2011 16:48:36 +0200 As a high-level comment it seems to me the organization of the specification needs some changing. The processing model is about how to deal with a "copy/paste/cut operation" it is not about firing an event (that is mainly part of it)

[Clipboard] Processing model feedback (and other)

As a high-level comment it seems to me the organization of the specification needs some changing. The processing model is about how to deal with a "copy/paste/cut operation" it is not about firing an event (that is mainly part of it). The events section meanwhile is about how users invoke a