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 455331 - Orca should not speak/braille greyed for frames and panels in mozilla
Orca should not speak/braille greyed for frames and panels in mozilla
Status: RESOLVED NOTGNOME
Product: orca
Classification: Applications
Component: general
2.19.x
Other All
: Normal enhancement
: ---
Assigned To: Joanmarie Diggs (IRC: joanie)
Orca Maintainers
Depends on:
Blocks: 404403 404409
 
 
Reported: 2007-07-09 22:40 UTC by Mike Pedersen
Modified: 2007-07-24 20:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Mike Pedersen 2007-07-09 22:40:37 UTC
Frequently in both firefox and thunderbird orca will speak greyed before panels and frames.  This information seems to be incorrect and quite miss-leading.  In these cases lets just not speak the greyed state.
Comment 1 Joanmarie Diggs (IRC: joanie) 2007-07-11 22:03:23 UTC
Turns out that Firefox and Thunderbird application frames lack STATE_SENSITIVE (which is causing us to say "grayed") and STATE_ENABLED.  When I looked at a bunch of other application frames with Accerciser, they all had these states.  I've filed a bug against Mozilla core asking for those states to be included/exposed. See: https://bugzilla.mozilla.org/show_bug.cgi?id=387732.

Marking this bug as blocked.   Mike, if you can find some panel examples that I can reproduce, please add them as a comment to this bug.  Thanks!
Comment 2 Joanmarie Diggs (IRC: joanie) 2007-07-14 23:29:43 UTC
These states are now being exposed, perhaps as a happy side effect of the states fix to https://bugzilla.mozilla.org/show_bug.cgi?id=387925.

With the latest Firefox and Thunderbird, Orca no longer says "grayed" for the frames, therefore I'm unblocking this bug.  Mike please let me know about the panels.  i.e. what else needs to be done in order to close this bug?
Comment 3 Mike Pedersen 2007-07-24 20:53:08 UTC
In the last functional mozilla builds this seems to be fixed.