W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2009

Re: Speeding up mutation events

From: David Bolter <david.bolter@utoronto.ca>
Date: Thu, 04 Jun 2009 16:26:31 -0400
Message-ID: <4A282DF7.1020806@utoronto.ca>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
CC: "www-dom@w3.org" <www-dom@w3.org>
(Resending from the correct account this time...  apologies if this 
reply shows up again.)

On 6/4/09 11:56 AM, Boris Zbarsky wrote:
> David Bolter wrote:
>> Thanks for this explanation. Would it be worthwhile figuring out
>> which, of all the possible old values a consumer of DOMAttrModified
>> might be interested in, in the wild? Then take this list and flesh
>> out the performance vs value, and agree on a subset?
>
> I'm not really quite sure how one would go about doing this, but I'm
> not going to say no to someone who volunteers to gather data!
>

Good point... I'm not sure how to get the data either.

>> Having old data for CharacterDataChanged events would allow better
>> live region support for assistive technology... not sure how to avoid
>> the string copy there...
>
> Assistive technology is presumably not being built on top of DOM
> events or their replacement, right?

Right. For now at least.

> And in particular, it can be designed on top of callbacks that assume
> the callee can be trusted to not screw things up (e.g. a "attribute
> about to change" notification that assumes the callee will not mess
> with the DOM).  Such assumptions simply cannot be made when calling
> into content script, of course.  Content script needs to always
> assumed to be hostile.

Yes an "attribute about to change" callback should work for my purposes :)

D
Received on Thursday, 4 June 2009 20:27:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:00 GMT