Closed Bug 1318263 Opened 9 years ago Closed 9 years ago

Cannot input with IME

Categories

(Focus-iOS :: General, defect, P1)

Product:
Focus-iOS
Component:
General
Platform:
Other
iOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Iteration:
1.13

People

(Reporter: bugzilla, Assigned: bnicholson)

Details

(Whiteboard: [MobileAS])

We cannot input Japanese (or any other languages which need IME to input) in the URL bar since it don't support IME. Even if we cannot support l10n, we should support i18n at least.
Same problem here in traditional Chinese input using Zhuyin.
Flags: needinfo?(bnicholson)
This is a pretty big deal -- I'd like to fix this for the next release if we can fit it.
Assignee: nobody → bnicholson
Status: NEW → ASSIGNED
Iteration: --- → 1.13
Flags: needinfo?(bnicholson)
Priority: -- → P1
Whiteboard: [MobileAS]
Yeah this is a big deal and it is preventing people from using the app in locales where IME is needed. How about this as something we do for 2.1 and then look for a more structural solution beyond that: For the locales that we know need IME, disable the autocompletion in the text field. We lose autocomplete, but we know most people start their browsing with a search. We can probably make a short list of locales.
Flags: needinfo?(bnicholson)
Dynamis, what does "Even if we cannot support l10n, we should support i18n at least" mean? Can you explain a bit more?
Flags: needinfo?(bugzilla)
(In reply to Stefan Arentz [:st3fan] from comment #3) > For the locales that we know need IME, disable the autocompletion in the > text field. Coped from Slack: Yeah, that’s similar to what I was planning. Getting provisional input to work correctly would be a pretty big change, and I think we’re too close to release to try that. I was hoping we could detect `markedText` though (similar to Firefox) rather than hardcode locales since there are a lot of locales to consider. We’ll want to look beyond just the l10n list we have — people can use Focus with their language’s keyboard even if it’s not localized for them. (In reply to Stefan Arentz [:st3fan] from comment #4) > Dynamis, what does "Even if we cannot support l10n, we should support i18n > at least" mean? Can you explain a bit more? He means that even if Focus isn't translated to a specific language (e.g., Japanese), Japanese users should still be able to use the app.
Flags: needinfo?(bugzilla)
Flags: needinfo?(bnicholson)
Version: unspecified → 2.1
master: de5a59a
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
How do I correspond the build number with commit? I just installed #421 and this bug is not fixed.
Flags: needinfo?(bnicholson)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Tim, can you give me steps to reproduce where multistage input isn't working? The latest build is working for me if I do the following: 1) Switch to the Japanese Kana keyboard. 2) Switch to the 3x3 A-Z key layout. 3) Type "hey" (GHI twice, DEF twice, WXYZ three times). The result is "hey", as expected, and marked blue text in the URL bar gets replaced with characters as I'm typing.
Flags: needinfo?(bnicholson) → needinfo?(timdream)
Sorry, false alarm, I installed and retested the old builds, and the first fixed version was #420. #421 and #424 also works. I am using Zhuyin IME keyboard with full keyboard layout (the new one that doesn't involve shift key). (#420 was also the first multilocale version so I must be distracted by too many changes)
Flags: needinfo?(timdream)
Great, thanks for the update!
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
I've confirmed with Japanese IME on Firefox Focus 3.0 RC3 (Build #439). Thanks!
You need to log in before you can comment on or make changes to this bug.