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 401889 - Orca does not speak backspaced characters in certain dialogs
Orca does not speak backspaced characters in certain dialogs
Status: RESOLVED FIXED
Product: orca
Classification: Applications
Component: speech
2.17.x
Other All
: High major
: 2.20.0
Assigned To: Willie Walker
Orca Maintainers
: 353434 477974 (view as bug list)
Depends on: 404714
Blocks:
 
 
Reported: 2007-01-28 23:15 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2008-07-22 19:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Joanmarie Diggs (IRC: joanie) 2007-01-28 23:15:15 UTC 
Steps to reproduce:

1. Press Alt F2 to get into the Run Application dialog
2. Type a few characters
3. Use backspace to remove the characters

Orca is not speaking the characters that are removed.

This can also be reproduced in certain Save As dialogs (e.g. Gedit's).  This seems to be true in both Edgy and Feisty.
Comment 1 Joanmarie Diggs (IRC: joanie) 2007-01-29 00:20:37 UTC 
Under the above circumstances, the any_data contains the current character rather than the character that was just removed.
Comment 2 Joanmarie Diggs (IRC: joanie) 2007-02-05 17:52:47 UTC 
Rich do you think that this is another gail/atk bug?  It doesn't seem to be an Orca bug, but I wasn't sure where to file it.  Thanks!
Comment 3 Rich Burridge 2007-02-05 18:14:55 UTC 
Yes, I predict it is. If the any_data value is invalid by the
time it gets to Orca, it points the finger at the sender (in
this case, a Gtk+ text field.) Could you please file a gail/gtk+
bug on this, and block this one against it? For extra points,
see if you can reproduce the problem in one of our infamous
standalone Python scripts. If you need some help with this, please
let me know. Thanks!
Comment 4 Joanmarie Diggs (IRC: joanie) 2007-02-05 19:28:59 UTC 
Thanks for the info Rich!  

Done (at least the filing and blocking bit).  As much as I would like to populate the world with our infamous scripts ;-) I'm afraid I'm facing some major work deadlines this week.  I'm hoping the description and use of at-poke to verify/reproduce the issue will be what they need.  If not, I'll work on a stand-alone script later on.
Comment 5 Mike Pedersen 2007-02-15 20:12:50 UTC 
Hi Joanie, have you had any response to your blocking bug on this?  Should we do any follow-up?
Comment 6 Joanmarie Diggs (IRC: joanie) 2007-02-15 20:18:18 UTC 
Bill made a comment; I asked for more info.  If you can nudge the folks who can make this change into making the change, by all means do so.  <grin>
Comment 7 Willie Walker 2007-05-22 14:04:39 UTC 
Is this a possible dup of bug 353434?
Comment 8 Joanmarie Diggs (IRC: joanie) 2007-05-22 15:25:33 UTC 
Actually, my guess is that bug 353434 is a dup of this one.  The issue in that bug is just one example of this problem.
Comment 9 Willie Walker 2007-05-25 15:10:21 UTC 
*** Bug 353434 has been marked as a duplicate of this bug. ***
Comment 10 Willie Walker 2007-05-25 16:27:16 UTC 
Removing target milestone from [blocked] bugs.  We have little control over them, so we're better off letting priority and severity be our guide for poking the related components.
Comment 11 Willie Walker 2007-05-29 16:31:35 UTC 
Mike has verified this as FIXED because of the fix to GAIL that Li did in bug 348466.  Closing.
Comment 12 Joanmarie Diggs (IRC: joanie) 2007-09-18 13:55:31 UTC 
*** Bug 477974 has been marked as a duplicate of this bug. ***