On Nov 5, 2010, at 6:40 PM, James Robinson wrote: > It also has worse performance characteristics since it means that the browser > would have to fire the DOMAttributeChangeRequestEvent synchronously when it > wanted to change the attribute and wouldn't be allowed to batch up the events > at all.
No need to batch because these are only triggered by discrete user actions, and don't even need to be fired unless the web app author has registered for the event. Also, please note that much of the time, these would not be used in a mainstream interface. For example, you're NOT going to getting a series of synchronous UIScrollRequests when the user scrolls a mouse wheel. For that, you'd receive a series of asynchronous WheelEvents or ScollEvents. You might however, receive a single UIScrollRequest when the user pressed the PageDown key.
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
