DO NOT REPLY [Bug 23744] New: - DOMSubtreeModified event thrown too early/often when modifing DOM through Range API

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23744>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23744

DOMSubtreeModified event thrown too early/often when modifing DOM through Range API

           Summary: DOMSubtreeModified event thrown too early/often when
                    modifing DOM through Range API
           Product: Xerces2-J
           Version: 2.5.0
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: DOM
        AssignedTo: xerces-j-dev@xml.apache.org
        ReportedBy: chris@dni.lu


When using Range.deleteContents(), the sequence of events that is fired contains
multiple "DOMSubtreeModified" events mixed between the more specific events.

This actually occurs when the Range 'contains' several Nodes and several
subnodes/character nodes.

AFAIK, this is not correct behaviour as described in the Mutation Events
specification.

According to the specification, the DOMSubtreeModified event should only be
invoked after all more specific events have been thrown.

This bug makes it impossible to determine when the sequence of events fired is
actually coming to an end, which is problematic and/or causing bad performance
of event handler.

Do you also consider this as a bug? Are there chances it will be fixed in a
future version?

Many thanks,
Regards,
Christian

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org