W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2012

Re: [UndoManager] What should a "native" automatic transaction expose?

From: Ojan Vafai <ojan@chromium.org>
Date: Fri, 6 Jul 2012 08:53:56 -0700
Message-ID: <CANMdWTu2BQW+EeLBDDXUJzL-E0q4BjyqQYVzrxT6SkDxJzGyMQ@mail.gmail.com>
To: Ryosuke Niwa <rniwa@webkit.org>
Cc: public-webapps <public-webapps@w3.org>, Ehsan Akhgari <ehsan@mozilla.com>, Jonas Sicking <jonas@sicking.cc>, Aryeh Gregor <ayg@aryeh.name>
On Wed, Jul 4, 2012 at 3:43 PM, Ryosuke Niwa <rniwa@webkit.org> wrote:

> Hi,
>
> In section 3.3 [1], we mention that the user editing actions and drag and
> drop need to be implemented as automatic DOM transactions. But it seems odd
> to expose executeAutomatic function in this case especially for drag & drop.
>
> I propose to set executeAutomatic null for those "native" automatic
> transactions but still expose label (set to whatever the Web browsers use
> in the edit menu).
>

Can we do the same for execute? We don't need to hold on to the execute
function once we've done the initial transaction, right?


>
> [1]
> http://dvcs.w3.org/hg/undomanager/raw-file/tip/undomanager.html#automatic-dom-transactions
>
> Best,
> Ryosuke Niwa
> Software Engineer
> Google Inc.
>
>
>
Received on Friday, 6 July 2012 15:54:49 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:53 GMT