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 448096 - [verified] Orca does not provide access to progress bars for FF3 downloads
[verified] Orca does not provide access to progress bars for FF3 downloads
Status: RESOLVED FIXED
Product: orca
Classification: Applications
Component: general
2.19.x
Other All
: Normal normal
: 2.20.0
Assigned To: Joanmarie Diggs (IRC: joanie)
Orca Maintainers
Depends on:
Blocks: 404403 438333
 
 
Reported: 2007-06-16 03:56 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2008-07-22 19:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Attachments
proposed patch (4.20 KB, patch)
2007-06-25 15:36 UTC, Joanmarie Diggs (IRC: joanie)
committed Details | Review

Description Joanmarie Diggs (IRC: joanie) 2007-06-16 03:56:52 UTC
This is a tracking bug for the following Firefox bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=384667 AT-SPI events not generated for all Firefox progress bars .
Comment 1 Joanmarie Diggs (IRC: joanie) 2007-06-25 15:36:57 UTC
Created attachment 90617 [details] [review]
proposed patch

We're getting the events now.  However, because Gecko prefers a range of 0-1 rather than 0-100, we're failing to announce updates because int(value.currentValue) will always be 0.  It seems we should compare and store the percentValue instead.

Also, according to what was decided in bug #438333:

          - When progress bar is at 100%, we should present it, regardless
            of the interval.

Doesn't this mean we need to do the check for 100% outside of the block beginning with:

                 if (currentTime - lastProgressBarTime) > \
                           settings.progressBarUpdateInterval:

?

Anyhoo, I made the above adjustments, along with some tweaks to Gecko.py and things seem to be working more or less as expected.  Note that we do not seem to get an event in Gecko.py when the progress bar hits 100% so that is not getting spoken.  I'll ask for that.

Rich, do you see/foresee any problems with the changes I made to handleProgressBarUpdate()?  Thanks!
Comment 2 Rich Burridge 2007-06-25 16:09:29 UTC
Your changes look good to me. I don't foresee any problems.
I suggest committing them, and then get Mike to test. Thanks for
doing this.
Comment 3 Joanmarie Diggs (IRC: joanie) 2007-06-25 16:24:20 UTC
Thanks Rich!  Patch committed.  Mike please test.
Comment 4 Mike Pedersen 2007-06-25 17:01:59 UTC
Nice fix.  thanks much
Comment 5 Joanmarie Diggs (IRC: joanie) 2007-06-25 17:09:51 UTC
Thank you.  Closing as FIXED.