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 550903 - Orca should read the list of files in the firefox file upload dialog
Orca should read the list of files in the firefox file upload dialog
Status: RESOLVED NOTGNOME
Product: orca
Classification: Applications
Component: general
2.23.x
Other All
: Normal normal
: 2.24.0
Assigned To: Joanmarie Diggs (IRC: joanie)
Orca Maintainers
Depends on:
Blocks: 404403
 
 
Reported: 2008-09-04 20:30 UTC by Mike Pedersen
Modified: 2008-10-02 05:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Mike Pedersen 2008-09-04 20:30:56 UTC 
1.  open a bug in bugzilla.

2.  create an attachment.

3.  press the browse button to pick a file to upload.

4.  Shift-tab back to the list of files.

5.  attempt to down arrow through the list.  

Notice that nothing is spoken/brailled.
Comment 1 Joanmarie Diggs (IRC: joanie) 2008-09-08 08:47:56 UTC 
Mike I'm afraid I'm going to need a debug.out. I just tried several times to reproduce the problem and couldn't. Actually I tried several times yesterday (or was it the day before?) which is how I found that braille monitor bug. But arrowing around in the dialog worked just fine.

I see some candidates for the issue you're describing in the default script's onActiveDescendantChanged() like:

1. Firefox lying to us and not exposing STATE_FOCUSED for parent (in which case we'd bail).

2. A speech.stop() -- maybe we're cutting off speech?? The last time, as I recall, where you had speech issues I couldn't reproduce, the magical step was to use espeak at a rate of 99.  Tried that, and I'm still hearing the items I'm arrowing amongst.

Thanks.

BTW, assuming you can reliably reproduce this problem and get me a debug.out before too long, it should be easy enough to fix before the week is out. So retargeting to 2.24.
Comment 2 Joanmarie Diggs (IRC: joanie) 2008-09-26 05:07:40 UTC 
Mike are you still seeing this problem?
Comment 3 Mike Pedersen 2008-10-01 21:31:07 UTC 
This now seems OK with latest firefox.
Comment 4 Joanmarie Diggs (IRC: joanie) 2008-10-02 05:10:59 UTC 
Cool, thanks Mike! I'm therefore going to close this one out. If the problem reappears, please re-open and I'll re-investigate. :-)