"j80m " wrote: > > But, I found something strange. > > In DOM2 Events, MutationEvent interface, initMutationEvent(~) > > public void initMutationEvent( String typeArg, > boolean canBubbleArg, > boolean cancelableArg, > Node relatedNodeArg, > String prevValueArg, > String newValueArg, > String attrNameArg);
Where did you get that from? This is out of date. This was changed before the DOM Level 2 spec becomes a Recommendation. See http://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-MutationEvent > But In Xerces (org.apache.xerces.dom.events.MutationEventImpl), > > public void initMutationEvent( String typeArg, > boolean canBubbleArg, > boolean cancelableArg, > Node relatedNodeArg, > String prevValueArg, > String newValueArg, > String attrNameArg > ***** short attrChangeArg); > > I'm just curious why attrChangeArg parameter is added. That's in line with the latest spec. -- Arnaud Le Hors - IBM Cupertino, XML Strategy Group
