On 6/30/11 2:56 PM, David Flanagan wrote:
I'll add my own possibly stupid question... Can we go in the opposite direction and fire mutation events immediately without queuing, but forbid any DOM modifications from the event callbacks?
Forbid DOM modifications to all DOMs? Or just one DOM? Is window.close() forbidden? Is spinning the event loop (e.g. sync XHR) forbidden?
This is actually a pretty hard problem to solve, and still wouldn't really solve the performance issues for DOM events....
-Boris
