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

Re: [UndoManager] Disallowing live UndoManager on detached nodes

From: Ryosuke Niwa <rniwa@webkit.org>
Date: Wed, 22 Aug 2012 18:49:13 -0700
Message-ID: <CABNRm62KNEzBB4-Hfidyu_EGq=bUEBSapvX36vBPcbyoW5B-Ew@mail.gmail.com>
To: Glenn Maynard <glenn@zewt.org>
Cc: Maciej Stachowiak <mjs@apple.com>, public-webapps <public-webapps@w3.org>, Kentaro Hara <haraken@chromium.org>, Sukolsak Sakshuwong <sukolsak@google.com>, Adam Barth <abarth@webkit.org>, Ehsan Akhgari <ehsan@mozilla.com>, Jonas Sicking <jonas@sicking.cc>, Olli Pettay <Olli.Pettay@helsinki.fi>, Ojan Vafai <ojan@chromium.org>
On Wed, Aug 22, 2012 at 5:55 PM, Glenn Maynard <glenn@zewt.org> wrote:

> On Wed, Aug 22, 2012 at 7:36 PM, Maciej Stachowiak <mjs@apple.com> wrote:
>
>> Ryosuke also raised the possibility of multiple text fields having
>> separate UndoManagers. On Mac, most apps wipe they undo queue when you
>> change text field focus. WebKit preserves a single undo queue across text
>> fields, so that tabbing out does not kill your ability to undo. I don't
>> know of any app where you get separate switchable persistent undo queues.
>> Thins are similar on iOS.
>>
>
> Firefox in Windows has a separate undo list for each input.  I would find
> a single undo list strange.
>

Internet Explorer and WebKit don't.

While we're probably all biased to think that what we're used to is the
best behavior, it's important to design our API so that implementors need
not to violate platform conventions. In this case, it might mean that
whether text field has its own undo manager by default depends on the
platform convention.

- Ryosuke
Received on Thursday, 23 August 2012 01:50:00 GMT

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