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 426242 - no accessibility support for input method
no accessibility support for input method
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Input Methods
2.10.x
Other Linux
: Normal enhancement
: ---
Assigned To: Hidetoshi Tajima
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2007-04-04 14:29 UTC by Akira TAGOH
Modified: 2018-02-10 04:34 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Akira TAGOH 2007-04-04 14:29:30 UTC
There are no way to know through a11y libraries what characters are input during preediting. this interferes to correct the words at the preedit line.
Comment 1 Matthias Clasen 2007-04-11 14:21:14 UTC
Do you have a proposal for required api additions ?
Comment 2 Akira TAGOH 2007-05-08 13:27:46 UTC
Yes. I'm thinking about a11y support at IM much more. it's an rough idea though, it would be a good idea to have APIs for dealing with:

- turning on/off IM
- peeking into preedit line
- moving the selection at the candidate window
- conversion and commit

Which is commonly used for the process on IM, and is relevant to the keybinding stuff because it's quite difficult to see which keys works for something without seeing the configuration at IMs and it prevents to work on a11y.
Comment 3 Matthias Clasen 2007-07-04 05:31:47 UTC
For turning on/off, see bug 346780
Comment 4 Matthias Clasen 2018-02-10 04:34:02 UTC
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.