[
https://issues.apache.org/jira/browse/XERCESC-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773505#action_12773505 ]
Scott Cantor commented on XERCESC-1168:
---------------------------------------
I'm in the middle of a security release, but when I have a chance I can try it.
Can we find out whether the fix requires that the original node be released, or just detached? If it's the former, the fix wouldn't be testable in my particular environment.
> getElementById succeeds after removeChild and release.
> ------------------------------------------------------
>
> Key: XERCESC-1168
> URL:
https://issues.apache.org/jira/browse/XERCESC-1168> Project: Xerces-C++
> Issue Type: Bug
> Components: DOM
> Affects Versions: 3.0.1
> Environment: Operating System: Windows NT/2K
> Platform: PC
> Reporter: juiceki
>
> After creating a DOMElement which looks like this (Note setIdAttribute was used
> on "Id") :
> <Object>
> <Tool Id="A"/>
> </Object
> after a call to object->removeChild( toolElement ) and toolElement->release
> the function getElementById( "A" ) still returns the removed node. Should this
> happen?
> Furthermore, if I exclude the call to "release" (above), and
> (re)add a new element with 'Id="A"' then a call to
> getElementById( "A" ) returns the previously removed (parent less) element
> rather than the new element added.
> If the "release" call was included in the above scenario, then the new element
> is returned as expected.
> I feel that this is a bug, perhaps I am using the API incorrectly.
> Feel free to contact me if you need clarification.
--
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:
c-dev-unsubscribe@...
For additional commands, e-mail:
c-dev-help@...
