W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2010

Resending: DOMCharacterDataModified:prevValue?

From: Travis Leithead <travil@microsoft.com>
Date: Thu, 1 Jul 2010 22:19:57 +0000
To: "www-dom@w3.org" <www-dom@w3.org>, Doug Schepers <schepers@w3.org>, "Olli@pettay.fi" <Olli@pettay.fi>
Message-ID: <9768D477C67135458BF978A45BCF9B3811971D@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
DOMCharacterDataModified event-should it provide a "prevValue" and "newValue"? The definition of the event<http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#event-type-DOMCharacterDataModified> [1] seems to indicate "no" (which is what other browsers have implemented), but the definition of<http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-Events-MutationEvent-prevValue> [2] "prevValue" and "newValue" seem to contradict that.

The third IE9 platform preview [3] is currently supporting supplying the prevValue/newValue, but at a large performance cost. I'd like to see this apparent contradiction resolved one way or the other. Thanks!

-Travis

[1] http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#event-type-DOMCharacterDataModified
[2] http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-Events-MutationEvent-prevValue
[3] http://ie.microsoft.com/testdrive/Default.html
Received on Thursday, 1 July 2010 22:20:45 GMT

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