You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org> on 2009/12/14 06:02:18 UTC
[jira] Resolved: (XERCESJ-1397) After invoking mutating methods
upon CharacterData, DOMCharacterDataModified events are always thrown even
if the content remains the same (i.e. no change happend)
[ https://issues.apache.org/jira/browse/XERCESJ-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Glavassevich resolved XERCESJ-1397.
-------------------------------------------
Resolution: Won't Fix
As discussed, making this change could break compatibility for some applications, so marking this as "Won't Fix".
> After invoking mutating methods upon CharacterData, DOMCharacterDataModified events are always thrown even if the content remains the same (i.e. no change happend)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: XERCESJ-1397
> URL: https://issues.apache.org/jira/browse/XERCESJ-1397
> Project: Xerces2-J
> Issue Type: Improvement
> Components: DOM (Level 2 Events)
> Affects Versions: 2.9.1
> Reporter: Ludger Bünger
> Attachments: DOMCharacterDataModifiedPatch.txt
>
>
> Invoking mutation methods upon the CharacterData interface (e.g. insertData, appendData, setNodeValue) always causes a DOMCharacterDataModified event to be thrown, even if the underlying character data remains the same (e.g. setting the same content twice).
> According to the DOM Level 2 specification (http://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-MutationEvent), the DOMCharacterDataModified is to be "fired after CharacterData within a node has been modified".
> It is debatable whether setting the same content twice falls under "CharacterData within a node has been modified" so i classified this issue as an improvement, not a bug.
--
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: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org