Closed
Bug 317944
Opened 20 years ago
Closed 18 years ago
URL bar not functional with UIM input method
Categories
(Firefox :: Address Bar, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: aligete, Unassigned)
References
Details
(Whiteboard: CLOSEME 06/27)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051118 Debian/1.4.99+1.5rc3.dfsg-1 Firefox/1.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051118 Debian/1.4.99+1.5rc3.dfsg-1 Firefox/1.5
UIM has to be activated. When tipying in UIM direct mode, only the first key pressed appears in the location bar. Visited links begining with that character appear below, but there is no way to continue typing any URL, following characters an deleted and visited links refreshed.
Reproducible: Always
Steps to Reproduce:
1. Activate UIM.
2. Type a letter.
3. Type another letter.
Actual Results:
Only the first character in the URL shows.
Expected Results:
Every pressed key should show in the location bar.
locale=es_ES
input method = UIM(direct)
Summary: URL bar no functional with uim input metrhod → URL bar not functional with UIM input method
Version: unspecified → 1.5 Branch
Comment 1•19 years ago
|
||
I can confirm this problem with Japanese locale: ja_JP.UTF-8 using UIM. When UIM is not active, Firefox works fine. Otherwise, the autocomplete box steals keyboard input and will not release it until I click somewhere.
Comment 2•19 years ago
|
||
*** Bug 331700 has been marked as a duplicate of this bug. ***
Comment 3•19 years ago
|
||
I've come up with a work-around after figuring out a little more about the problem.
Firefox, for reasons I don't yet understand, doesn't play nicely with UIM. Others have reported similar issues with Thunderbird, et al. in various places on the Net. Most of what I've read has been related to crashes with SCIM, but apparently it's nothing new that Firefox doesn't like GTK_IM_MODULE="uim" . I would fathom a guess, due to the SCIM problems, that Firefox 1.5.x only works well with the old XIM way of doing things. Strange, because 1.0.x works fine.
The work-around: write a simple wrapper script that starts Firefox with GTK_IM_MODULE="xim" and run uim-xim. The LANG variable also needs to be set to the target language's locale, or input won't work using the XIM. There are some font issues I don't know how to fix yet (Japanese gui fonts look really ugly when LANG=ja_JP.UTF-8, but not in en_US locale; UTF-8 webpages appear to use Japanese font settings in textareas like this one), but until UIM is fixed, at least there's a solution to the input problem in Firefox 1.5.x.
I'm sorry if this is the wrong place for such information, but I hope it can help somebody.
Comment 4•19 years ago
|
||
Bump.
Can someone mark this as 'new' instead of 'unconfirmed?' It's been confirmed, and is really the only thing keeping me from switching to v1.5.x :)
Comment 5•18 years ago
|
||
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Whiteboard: CLOSEME 06/27
Comment 6•18 years ago
|
||
It works for me, that much I can say. I am closing the bug now as WFM. Feel free to reopen with more information if this is still a problem for you.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•