On Wed, Aug 18, 2010 at 2:31 PM, Ojan Vafai <ojan@chromium.org> wrote:

My intuition is that very few sites or extensions actually depend on them being synchronous.

I agree. I worked on some extension app this spring but all I needed to know was when the subtree of certain nodes change so that I can go ahead and modify them. There was no need to prevent the change or catch synchronously. That alone, I think would address the majority of mutation-event related

crashing and does not prevent us from adding newer, better APIs.

Agreed. If we can postpone all mutation events until the end of each compose edit command, we'll be able to prevent the majority of crashes. I think reducing mutation event support down to just DOMSubtreeModified, and

...

firing it only at the very end of operations that should be atomic, would greatly reduce the risk of mutation-event-induced crashing, but would probably still serve the key use cases.

Agreed.

Ditto. Best, Ryosuke Niwa Software Engineer Google Inc.