[
https://issues.apache.org/jira/browse/XERCESJ-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Glavassevich updated XERCESJ-1445:
------------------------------------------
Affects Version/s: 2.9.1
> if an Element node is renamed resulting in a node replacement, the range,
> nodeIterator and identifier data structure should be updated.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: XERCESJ-1445
> URL: https://issues.apache.org/jira/browse/XERCESJ-1445
> Project: Xerces2-J
> Issue Type: Bug
> Components: DOM (Level 3 Core)
> Affects Versions: 2.9.1
> Reporter: Ludger Bünger
> Attachments: RenameReplaceNodeIdentifierRangeIteratorUpdatePatch.txt
>
>
> If an element node is renamed resulting in a node replace, certain internal
> data structures are not updated.
> While userdata and event listeners are transfered from the previous to the
> new node, the following are not:
> 1. Ranges containg the element as a start or endContainer do update as if the
> node has been removed.
> 2. NodeIterators containing the element as a iteration point do update as if
> the node has been removed.
> I think in both cases the range/node iterator should be treated such that the
> new element replaces the old element without range update.
> 3. the identifier map containing all nodes associated with an identifier
> attribute is partially updated: entries for the old node are removed but no
> mapping to the new node is inserted.
> Attached please find a patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
