Closed
Bug 714198
Opened 13 years ago
Closed 13 years ago
Can't check if a11y is enabled in GNOME 3
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 693343
People
(Reporter: chrisccoulson, Assigned: chrisccoulson)
References
Details
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
Currently, there is code in accessible/src/atk/nsApplicationAccessibleWrap.cpp and widget/src/gtk2/nsWindow.cpp to check if a11y is enabled by looking at the "/desktop/gnome/interface/accessibility" key in GConf. This doesn't work in GNOME 3 because of the transition to GSettings**. This seems to be the last feature depending on GConf now. ** It may still work on some systems due to the GSettings -> GConf bridge, but this has been removed already (http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=f4ef02038a1f57edf7a23ba91829f15cddfc7eff)
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → chrisccoulson
Assignee | ||
Comment 1•13 years ago
|
||
See Also: → https://launchpad.net/bugs/857153
Comment 3•13 years ago
|
||
probably karlt for the gtk2 widget stuff, and maybe surkov or dbolter for the a11y stuff... or maybe just karlt alone.
Comment 4•13 years ago
|
||
(In reply to Reed Loden [:reed] (very busy) from comment #3) > probably karlt for the gtk2 widget stuff, and maybe surkov or dbolter for > the a11y stuff... or maybe just karlt alone. actually, me or Ginn Chen are probably the better a11y people here, and I think one of us should look at that sort of thing. That said we're already working on this in bug 693343, if you'd like to help figure out the shutdown hang were having trouble with there that would be great!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•