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

Mutation Events and Null values

From: Brad Pettit <bradp@microsoft.com>
Date: Tue, 14 May 2002 10:35:36 -0700
Message-ID: <3013537455C0D1459746B2AE2DF47AEA0521F1B6@svc-msg-01.northamerica.corp.microsoft.com>
To: <www-dom@w3.org>
In the documentation for initMutationEvent, the descriptions of
newValueArg and attrNameArg specify their values may be NULL. The spec
not clear as to whether this means the value is optional, or only that
it may be
NULL if it is not used for specific MutationEvent types, such as
prevValueArg is
not used for a DOMSubtreeModified MutationEvent.

In order to be DOM-compliant, are prevValueArg, newValueArg and
required to be non-null for those MutationEvent types for which they

It seems like supporting this requirement for prevValue could degrade
overall UA performance since it could significantly increase the memory
requirements and event traffic associated with document modification.
In many cases, I could see the event being useful without the previous
The impact of newValue isn't as significant since it should also be the
node's current value, but it does seem redundant for the same reason.

Brad Pettit
Microsoft Corp.
Received on Tuesday, 14 May 2002 13:36:15 UTC

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