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

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!

-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