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 "Ludger Bünger (JIRA)" <xe...@xml.apache.org> on 2009/10/01 18:41:23 UTC
[jira] Created: (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)
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
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
[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)
Posted by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org>.
[ 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
[jira] Commented: (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)
Posted by "Ludger Bünger (JIRA)" <xe...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XERCESJ-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784744#action_12784744 ]
Ludger Bünger commented on XERCESJ-1397:
----------------------------------------
Ok, I agree that backwards compatibility is important and leaving this the way it currently is does no harm.
We should close the issue.
> 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
[jira] Commented: (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)
Posted by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XERCESJ-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784615#action_12784615 ]
Michael Glavassevich commented on XERCESJ-1397:
-----------------------------------------------
It's possible that applications are relying on the current behaviour. Think of the 'touch' command in Unix. Doesn't change the contents but gets you a new modification timestamp. I can imagine users depending on this (whether it's in the spirit of the spec or not) so not sure we could make this change. I tend to err on the side of backwards compatibility for grey areas.
> 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
[jira] Closed: (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)
Posted by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XERCESJ-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Glavassevich closed 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)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> 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
[jira] Updated: (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)
Posted by "Ludger Bünger (JIRA)" <xe...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XERCESJ-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ludger Bünger updated XERCESJ-1397:
-----------------------------------
Attachment: DOMCharacterDataModifiedPatch.txt
Please find attached a patch providing support for an additional character data content comparison before applying any dom mutation and firing the respective events.
> 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