W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2012

Re: [whatwg] Exceptions in UndoManager

From: Alex Vincent <ajvincent@gmail.com>
Date: Wed, 30 May 2012 08:15:30 -0700
Message-ID: <CAEZ8441PmwyFHP32v9G=Z72frJvdVu9uxYP6zoLaXWfkvSWvSQ@mail.gmail.com>
To: Ryosuke Niwa <rniwa@webkit.org>
Cc: whatwg@whatwg.org, Ojan Vafai <ojan@chromium.org>, Jonas Sicking <jonas@sicking.cc>, Olli Pettay <Olli.Pettay@helsinki.fi>, Ehsan Akhgari <ehsan@mozilla.com>
Sorry, I hit send prematurely.  Let me try again in a few minutes.

On Wed, May 30, 2012 at 8:15 AM, Alex Vincent <ajvincent@gmail.com> wrote:

> My first concern is "what state will the UndoManager be in when an
> exception happens?"  There may be transactions that were undone, cropped
> off
>
>
> On Wed, May 30, 2012 at 12:03 AM, Ryosuke Niwa <rniwa@webkit.org> wrote:
>
>> When an exception is thrown within transact(), the most sane behavior
>> appears to be rolling back all DOM changes that have made thus far (this in
>> turn may also fail due to mutation events, etc...). Also this is not
>> possible with manual transactions because browsers don't keep track of
>> what's happening in the DOM, etc...
>>
>> So how about just firing an event like DOMTransactionException at the
>> undo scope host to let scripts handle them?
>>
>
> --
> "The first step in confirming there is a bug in someone else's work is
> confirming there are no bugs in your own."
> -- Alexander J. Vincent, June 30, 2001
>



-- 
"The first step in confirming there is a bug in someone else's work is
confirming there are no bugs in your own."
-- Alexander J. Vincent, June 30, 2001
Received on Wednesday, 30 May 2012 15:16:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:08 GMT