GTK+ 1.x (old stable version) had a bug and exhibited this exactly bug that
Firefox has. However, it has been resolved in GTK+ 2.x, therefore it looks good
to give control to GTK+ to handle input.
For a summary, see http://mail.gnome.org/archives/gnome-i18n/2002-February/msg00051.html
Solving this core issue can clear up quite a few bugzilla entries.
The following Bugzilla bugs might be resolved through this issue:
1. "+ and - Keyboard accelerators inaccessible on international keyboards /bugzilla. mozilla. org/show_ bug.cgi? id=88380
(larger/smaller font size)"
https:/
2. "some control key sequences don't generate the correct event (ctrl-enter /bugzilla. mozilla. org/show_ bug.cgi? id=50255
...)"
https:/
3. "can't use gtk2 input modules ?" /bugzilla. mozilla. org/show_ bug.cgi? id=164793
https:/
I think the following three are as well related to the core problem discussed here: /bugzilla. mozilla. org/show_ bug.cgi? id=98376 /bugzilla. mozilla. org/show_ bug.cgi? id=218155 /bugzilla. mozilla. org/show_ bug.cgi? id=214412
a. Unable to input Latin-1 chars using US keyboard with input locale set
to CJK
https:/
b. Gtk2 XIM : Multi input context is not separated
https:/
c. No way to switch the GTK input modules
https:/
extract: "Yeah, SCIM and IIIIMF should 'solve' this problem without
anything changed on
the part of Mozilla. "
GTK+ 1.x (old stable version) had a bug and exhibited this exactly bug that mail.gnome. org/archives/ gnome-i18n/ 2002-February/ msg00051. html
Firefox has. However, it has been resolved in GTK+ 2.x, therefore it looks good
to give control to GTK+ to handle input.
For a summary, see
http://
Solving this core issue can clear up quite a few bugzilla entries.