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 155506 - gnopernicus does not speak disabled menu items
gnopernicus does not speak disabled menu items
Status: RESOLVED NOTABUG
Product: gnopernicus
Classification: Deprecated
Component: speech
unspecified
Other All
: Normal normal
: ---
Assigned To: mp
mp
AP1
Depends on:
Blocks:
 
 
Reported: 2004-10-15 14:09 UTC by padraig.obriain
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description padraig.obriain 2004-10-15 14:09:36 UTC
1) Invoke gnopernicus, enable speech in it. 
2) Open gnome-terminal. 
3) Click on Edit menu. 

It does not read the disabled submenu items like, copy. 
It does not read the disabled submenu items like, close tab.

In some other applications, like mozilla even disabled menu items will be read
as disabled. 

expected result:
Even disabled items shall be sent to reader, so that a blind user can hear it,
even though he won;t be able to use it.
Comment 1 korn 2004-10-18 00:41:53 UTC
The step-by-step instructions are insufficient.  If the tester is arrowing
through the menu, and such arrowing skips over the disabled menus, then this is
NOT a bug and should be closed.  Tester, please tell us what is going on?
Comment 2 Dana Ormenisan 2004-10-18 07:04:22 UTC
In mozilla, when user is arrowing through the menu, a 'focus:' event is fired
for every menu item (even if it is enabled or disabled). This is the reason why
gnopernicus is reading the disabled menu items. 
In gtk apps (i.e. gnome-terminal, gedit, ...), only the enabled menu items are
focused so gnopernicus can not read the disabled menu items.

This is certainly not a gnopernicus bug. Should it be closed as NOTABUG or
transferred in the right place for further evaluations? 
Comment 3 padraig.obriain 2004-10-18 10:22:29 UTC
This behavior sounds like a bug in mozilla.
Comment 4 korn 2004-10-18 15:17:15 UTC
When we found and discussed this issue (easily over a year ago), I believe we
decided that this is simply different and legal behavior, and so long as
Gnopernicus reports what is going on all is OK.  That was when we were less
comfortable changing general/UI behavior in apps.

I think this is worth discussing on the mozilla mailing list, and I'll do so. 
But I'm still not prepared to argue that this is a mozilla bug yet.
Comment 5 louie zhao 2004-10-19 06:00:24 UTC
I agree with Peter. This is not a gnopernicus bug and also not a A11y bug for
both terminal and mozilla. This is caused by different behaviour of
applications. Arguing which kind of behaviour is correct may have no result in
short term. It's beyond the scope of current a11y work.