Re: Mutation events replacement

On Sat, Jul 2, 2011 at 7:07 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
>
> The numbers above are made up, of course; it would be useful to have some
> hard data on the actual use cases.
>
> Maybe we need both sorts of APIs: one which generates a fine-grained change
> list and incurs a noticeable DOM mutation performance hit and one which
> batches changes more but doesn't slow the browser down as much...
>

Maybe we'll have a boolean that indicates whether an observer wants a
full-list or not when the observer is attached?

- Ryosuke