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 404714 - Text entry should expose deleted character when using Backspace
Text entry should expose deleted character when using Backspace
Status: RESOLVED DUPLICATE of bug 313954
Product: gtk+
Classification: Platform
Component: Widget: Other
2.10.x
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 401889
 
 
Reported: 2007-02-05 19:23 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2007-08-02 04:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Joanmarie Diggs (IRC: joanie) 2007-02-05 19:23:17 UTC
This was originally reported as an Orca bug (please see bug #401889).

When a character is removed via Backspace from a text entry field, the character that was removed should be exposed through at-spi in the event's any_data.  What is being exposed in the any_data is the character with focus.  This is problematic for screen readers which traditionally speak the character that was just removed as a result of Backspace being pressed.

Steps to reproduce/verify:

1. Launch at-poke
2. Check the "log events" checkbox
3. In the resulting "accessible events" window, expand "object" 
   and check the "text-changed" text box.
4. Get into either of the following dialogs:
   a. Run Application
   b. Gedit's Save As dialog
5. In the text entry field, type some text.
6. Use Backspace to remove the characters.  Notice that the 
   "change string" is empty when you Backspace from the end
   of what you typed; otherwise it contains the current char.
Comment 1 bill.haneman 2007-02-14 14:12:39 UTC
I think this is a duplicate of either a gtk+ bug or an atk/gail problem.

I think it's a result of gtk+ emitting its delete events in an idle handler, so that by the time gail sees the event, the deleted data is already unavailable.

Fixing may require a complex cacheing scheme (inside gail?), or else at least adding some "deleted stuff" data to the affected gailtext object.
Comment 2 Joanmarie Diggs (IRC: joanie) 2007-02-14 15:35:22 UTC
Hi Bill.  Thanks for the explanation!

Silly/newbie question:  We don't have this problem with the text widget; just the entry widget.  So.... Could the entry widget just do whatever magic the text widget does? (Or is that the complex cacheing scheme or addition of some "deleted stuff" data to which you are referring?)
Comment 3 Joanmarie Diggs (IRC: joanie) 2007-08-02 04:30:34 UTC
This no longer seems to be an issue because of the fix to bug 313954.  Marking it as a dup.

*** This bug has been marked as a duplicate of 313954 ***