- From: Alex Vincent <ajvincent@gmail.com>
- Date: Wed, 30 May 2012 08:15:08 -0700
- 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>
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
Received on Wednesday, 30 May 2012 15:15:42 UTC