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=17590>. 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=17590 Range.deleteContents on range enclosing single text node causes range offsets to be incorrectly fixed-up (re-submit) Summary: Range.deleteContents on range enclosing single text node causes range offsets to be incorrectly fixed-up (re- submit) Product: Xerces2-J Version: 2.3.0 Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: DOM AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] In bug 3221 (August 2001!), I submitted the following problem with xerces 1.4.3 'In xerces-j upto and including version 1.4.3, calling deleteContents causes the range to have its start and end offsets set to zero, when they should be set to the ranges original start offset. Problem appears to be in RangeImpl.traverseSameContainer where the text is removed by a call to setNodeValue: fStartContainer.setNodeValue( s.substring(0, fStartOffset ) + s.substring(fEndOffset) This in turn causes Range.receiveReplacedText to be called which sets the offsets to 0. Changing the setNodeValue call to ((TextImpl)fStartContainer).deleteData(fStartOffset, fEndOffset-fStartOffset) ; Seems to correctly fix the offsets' This bug is still present in 2.3.0! By report seems to have been completely ignored, which doesn't inspire confidence. Any chance of someone lookngi into this time? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
