[Bug swing/24192] New: DocumentEvents aren't being fired properly

[abalkiss at redhat dot com]

The testcase below shows the difference between the DocumentEvents that we are
currently sending and those that we should be sending after a text component is
updated.  To summarize, we are sending REMOVE events when they shouldn't be,
and we are not submitting the proper ElementChange with our DocumentEvents.

****Testcase expected output:
INSERT UPDATE
DocEvent type: javax.swing.text.AbstractDocument$DefaultDocumentEvent
offset: 0
length: 175
doc length: 175
type: INSERT
added child from: 0 to: 36
added child from: 36 to: 97
added child from: 97 to: 134
added child from: 134 to: 176
removed child from: 0 to: 176


***Testcase actual output:
REMOVED UPDATE
DocEvent type: javax.swing.text.AbstractDocument$DefaultDocumentEvent
offset: 0
length: 0
doc length: 0
type: REMOVE
The ElementChange is null


INSERT UPDATE
DocEvent type: javax.swing.text.AbstractDocument$DefaultDocumentEvent
offset: 0
length: 175
doc length: 175
type: INSERT
The ElementChange is null


The testcase will be attached in the next message.


-- 
           Summary: DocumentEvents aren't being fired properly
           Product: classpath
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: swing
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: abalkiss at redhat dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24192