After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 105969 - The JABG should be generating detailed information for text-changed events.
The JABG should be generating detailed information for text-changed events.
Status: RESOLVED OBSOLETE
Product: at-spi
Classification: Platform
Component: javabridge
unspecified
Other Linux
: Normal major
: ---
Assigned To: At-spi maintainer(s)
At-spi maintainer(s)
AP3
: 110245 111431 (view as bug list)
Depends on:
Blocks: 111999
 
 
Reported: 2003-02-13 10:49 UTC by Darren Kenny
Modified: 2014-11-13 17:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Darren Kenny 2003-02-13 10:49:56 UTC
More detail is required for text-changed events from the JABG.

At present all that is sent is:

    object:text-changed     + offset

Really what is needed is:

    object:text-changed:<insert|delete|replace>

    + start-offset
    + end-offset
    + CORBA Any with a String of the changed text.
Comment 1 Darren Kenny 2003-03-19 14:55:41 UTC
According the the link:

http://developer.gnome.org/doc/API/2.0/atk/atktext.html#ATKTEXT-TEXT-CHANGED

the second parameter is not the end-offset, but the length of the
change.

This ties with what I see when I use a GTK application and monitor the
events being generated.

Comment 2 Calum Benson 2003-04-03 15:01:27 UTC
Updating status_whiteboard field to reflect A11Y team's assessment 
of accessibility impact.
Comment 3 Calum Benson 2003-04-03 15:14:54 UTC
Woops, don't need to track this one with the status_whiteboard field.
Comment 4 Darren Kenny 2003-04-24 08:43:03 UTC
*** Bug 111431 has been marked as a duplicate of this bug. ***
Comment 5 Darren Kenny 2003-04-28 15:00:15 UTC
For the record, as Adi mentioned, there is a bug in IssueZilla against
SO to fix the generation of event detail there also:

The issue described in this report depends on
IssuZilla's(http://www.openoffice.org) bug 13677:
http://www.openoffice.org/project/www/issues/show_bug.cgi?id=13677

Comment 6 Darren Kenny 2003-04-28 15:01:34 UTC
*** Bug 110245 has been marked as a duplicate of this bug. ***
Comment 7 padraig.obriain 2003-05-16 10:29:36 UTC
Java bug 4839950 has been raised about Java not providing enough
information. The JABG may have to cache the previous text.

I have reduced the priority of this bug and added it to the tracking
bug 111999.
Comment 8 bill.haneman 2003-05-16 18:39:53 UTC
Padraig: why did you reduce the priority of this bug?  It's a blocker
for reasonable accessibility of Java apps.
Comment 9 padraig.obriain 2003-05-22 07:46:40 UTC
Nothing can be done about this bug until the Java bug is fixed.
Comment 10 Calum Benson 2003-08-07 16:16:11 UTC
Apologies for spam... marking as GNOMEVER2.3 so it appears on the official GNOME
bug list :)
Comment 11 Calum Benson 2004-10-21 16:51:22 UTC
Apologies for spam-- ensuring Sun a11y team are cc'ed on all current a11y bugs.
 Filter on "SUN A11Y SPAM" to ignore.
Comment 12 Calum Benson 2006-04-26 17:05:25 UTC
Apologies for spam... ensuring Sun a11y folks are cc'ed on all current accessibility bugs.
Comment 13 André Klapper 2012-02-26 10:44:21 UTC
[Resetting QA Contact to newly introduced "at-spi-maint@gnome.bugs". 
Reason: So far it was impossible to watch changes in at-spi bug reports without following all the specific persons (Li Yuan, Bill Haneman, Jeff Wai, ...) and also their activity outside of at-spi reports.

IMPORTANT: Anyone interested in following all bug activity (including all maintainers) must watch the "at-spi-maint@gnome.bugs" dummy user by adding it to the 'Users to watch' list under Preferences->Email preferences. This is also the default procedure nowadays in GNOME when setting up new products.]
Comment 14 André Klapper 2013-08-14 10:07:31 UTC
[Mass-resetting default assignee, see bug 705890. Please reclaim this bug report by setting the assignee to yourself if you still plan to work on this. Thanks!]
Comment 15 Magdalen Berns (irc magpie) 2014-11-13 17:31:15 UTC
I'm going to go ahead and close this because it concerns a very old version.
Feel free to open a new bug if the problem persists.