Issue 34527

Summary:	Incorrect informations (details) sent by 'object:text-changed:delete' at-spi event
Product:	ui	Reporter:	dormenisan <do>
Component:	AccessBridge	Assignee:	nospam4obr
Status:	CLOSED NOT_AN_OOO_ISSUE	QA Contact:	issues@ui <issues>
Severity:	Trivial
Priority:	P2	CC:	issues
Version:	OOo 1.0.0	Keywords:	accessibility
Target Milestone:	---
Hardware:	All
OS:	All
Issue Type:	DEFECT	Latest Confirmation in:	---
Developer Difficulty:	---

Description dormenisan 2004-09-23 08:01:27 UTC

When user deletes one(some) char(s)an at-spi 'object:text-changed:delete'
event is fired. The two details of this event should provide informations about
the current offset (after the char was deleted) and the number of deleted chars.
This is the behavior in GTK apps and Swing JTextComponent text (e.g. Stylepad).

Currently, in SO these details looks like:
  detail1=offset after the chars were deleted
  detail2=offset before delete the chars (no of deleted chars is needed)

This bug causes gnopernicus bug http://bugzilla.gnome.org/show_bug.cgi?id=151579

Comment 1 nospam4obr 2004-09-23 08:31:28 UTC

The notion of startIndex / endIndex corresponds exactly to the new interfaces
introduced in Java 1.5 (see http://java.sun.com/j2se/1.5.0/docs/api/index.html),
so I believe this should be fixed in the JABG.

Comment 2 billhaneman 2004-09-23 10:57:19 UTC

please reopen, as we cannot yet introduce a 1.5 dependency in the JABG;
therefore the pre-1.5 APIs still need to work properly.  It seems they do not,
based on Dana's bug report.

Comment 3 nospam4obr 2004-09-23 11:34:20 UTC

I am not saying that JABG should introduce Java 1.5 structures; we already have
a a private protocol as workaround for the missing AccessibleTextSequence in
Java 1.4 in place, it just doesn't work correctly: please see
bridge/org/GNOME/JavaBridge.java line 612 ff..

So this can easily be fixed inside JABG.

Comment 4 nospam4obr 2004-09-27 15:51:00 UTC