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 119174 - Turning on accessiblity support. What is the right way ?
Turning on accessiblity support. What is the right way ?
Status: RESOLVED NOTABUG
Product: libgnome
Classification: Deprecated
Component: general
HEAD
Other Linux
: Normal normal
: ---
Assigned To: libgnome maintainer
libgnome maintainer
Depends on:
Blocks:
 
 
Reported: 2003-08-05 14:59 UTC by Arvind S N
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Arvind S N 2003-08-05 14:59:44 UTC 
To get accessibility support we should either have
GNOME_ACCESSIBILITY=1 or set the /desktop/gnome/interface/accessibility key
to true.

Setting key becomes redundant when GNOME_ACCESSIBILITY is present in the
environment.

The questions are
a) Should we consider both before deciding not to turn on accessibility ?

b) If the answer to (a) is GNOME_ACCESSIBILITY takes precedence, then we
   should not be suggesting the key approach to users for setting up
   accessibility  support. Since it will make no difference once
   the env variable comes in to picture.

Thoughts ?
Comment 1 bill.haneman 2003-08-25 15:13:57 UTC 
I think we should maintain the status quo, since the env variable is
an interface which we should deprecate but should not remove.

the gconf key is the preferred mechanism and has been since shortly
after the start of the accessibility work.

I don't see any value in changing the current, slightly redundant,
mechanism.

- Bill
Comment 2 Kjartan Maraas 2004-03-25 13:17:24 UTC 
Bill, does that mean this bug is a WONTFIX?
Comment 3 bill.haneman 2004-03-25 13:51:01 UTC 
I'd say NOTABUG