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

Regards--in case Doug is back and the D3E telecon is on...

From: Travis Leithead <travil@microsoft.com>
Date: Wed, 16 Jun 2010 17:49:18 +0000
To: "www-dom@w3.org" <www-dom@w3.org>, Doug Schepers <schepers@w3.org>, "Olli@pettay.fi" <Olli@pettay.fi>
Message-ID: <9768D477C67135458BF978A45BCF9B380FC05C@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com>
Just in case we have the DOM L3 Events telecon today (I'm too lazy to look it up), I have a conflict and can't make it. However, I had previously raised some outstanding bugs in the current spec that I would love addressed-and one other thing has come up recently:

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.

IE9 internal builds are 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!


[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
Received on Wednesday, 16 June 2010 17:50:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:16 UTC