GNOME Bugzilla – Bug 343035
Orca: backspace isn't speaking in composer subject field
Last modified: 2006-08-29 19:09:10 UTC
Please describe the problem: There is no feedback to indicate which characters are being erased. I have noted this in the subject field, but it may be an issue in other fields as well. Backspace works as expected in the body of the message. Steps to reproduce: 1.Enters some text into the subject field, and then begin erasing it using backspace. Actual results: When backspace is pressed, nothing is spoken. Expected results: Backspace should speak the character that is being deleted. Does this happen every time? yes Other information:
Transferring to Evolution for further investigation. Orca (in default.py in the onTextDeleted() method) is looking at the any_data.value() field of the event to get the character that's just been deleted. This works fine when in the main body of the new mail message, but doesn't work correctly in the To, Cc or Subject fields (it contains the character to the right or where the text caret is).
Same problem with Evolution 2.6.0 as well. Adjusting version field.
i assume this is about the message composer, right? this does not happen here, i assume this only happens when using orca?
Yes, in the message composer. Yes, when using Orca. Orca relies on the accessibility information it can get from at-spi. The specific Orca code in this case is at: http://cvs.gnome.org/viewcvs/orca/src/orca/default.py?annotate=1.150 at line 1423 in the onTextDeleted() method: 1420 : richb 1.139 if string == "BackSpace": 1421 : richb 1.142 # Speak the character that has just been deleted. 1422 : richb 1.139 # 1423 : richb 1.142 character = event.any_data.value() What event.any_data.value() should return in the character that has just been deleted when the user enters Backspace. This works just fine in the main message body of the Evolution compose window. It doesn't work correctly in the To:, Cc: and Subject: fields. In those cases, it contains the character to the right of where the cursor is.
I see there is already any bug open with the same problem (currently with the atk/gail maintainers. Closing this one as a duplicate. *** This bug has been marked as a duplicate of 348466 ***