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 528644 - Orca should indicate when an autocomplete list has appeared in FF
Orca should indicate when an autocomplete list has appeared in FF
Status: RESOLVED FIXED
Product: orca
Classification: Applications
Component: general
2.21.x
Other All
: Normal enhancement
: 2.24.0
Assigned To: Joanmarie Diggs (IRC: joanie)
Orca Maintainers
Depends on:
Blocks: 404403
 
 
Reported: 2008-04-17 20:01 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2008-06-03 20:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Attachments
revision 1 (1.49 KB, patch)
2008-05-29 00:24 UTC, Joanmarie Diggs (IRC: joanie)
committed Details | Review

Description Joanmarie Diggs (IRC: joanie) 2008-04-17 20:01:16 UTC
Steps to reproduce:

1. Give focus to the search autocomplete in FF's toolbar

2. Type a common-enough, short string (e.g. "this")

3. Press Down Arrow

The search engine (e.g. google) has made suggestions based on what you typed. A sighted user knows that this has occurred because the list wasn't there before and now it is. :-) A user who is blind has to suspect that this might have taken place and then Down Arrow to see if he/she was correct.  It might be nice if Orca indicated when this has occurred.

Thoughts and questions:

1. It should be optional and/or maybe only spoken at the "verbose" level

2. What do we want to do for braille?
Comment 1 Mike Pedersen 2008-05-13 16:47:37 UTC
I wonder if perhaps we should do something like what we do for the firefox find dialog.  Maybe after the user has typed 4 characters we speak the first item in the list.  If the user keeps typing and the list changes we could speak the new first item.  

I don't think we should change the braille display at all based on the autocomplete information because the user will expect to see the text he/she is typing. 
thoughts?  
Comment 2 Joanmarie Diggs (IRC: joanie) 2008-05-13 22:15:40 UTC
Mike and I discussed this via the phone.  The situation with autocompletes is that when they appear, nothing is selected.  They're just there waiting for the user to give it focus.  Therefore we are planning on the following:

1. If the user did not cause it to appear (i.e. he/she was just 
   typing):

  a. At the verbose verbosity level, we'll speak "autocomplete"

  b. At the brief verbosity level, we'll not present it.

2. If the user did cause it to appear (i.e. by pressing Alt+Down),
   we'll speak "autocomplete" no matter what as a way to confirm
   that the thing has appeared (because still nothing will be 
   selected).
Comment 3 Joanmarie Diggs (IRC: joanie) 2008-05-29 00:24:41 UTC
Created attachment 111693 [details] [review]
revision 1

This seems to get the job done.  Pylinted already.  Will regression test it now.  Mike please see if this does what you think it should.  Thanks!
Comment 4 Joanmarie Diggs (IRC: joanie) 2008-05-29 03:21:39 UTC
Passes the regression tests.
Comment 5 Mike Pedersen 2008-05-29 19:30:02 UTC
I like this.  It is possible for the fast typeist to miss this message but it doesn't matter because they still here the first item as it appears.  
Comment 6 Joanmarie Diggs (IRC: joanie) 2008-05-29 20:47:39 UTC
Thanks Mike.  Patch committed to trunk.  Moving to pending.