Closed
Bug 590602
Opened 14 years ago
Closed 14 years ago
Support input method changing in Fennec
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(fennec2.0b3+)
VERIFIED
FIXED
Tracking | Status | |
---|---|---|
fennec | 2.0b3+ | --- |
People
(Reporter: ashah, Assigned: wesj)
References
Details
(Keywords: inputmethod, Whiteboard: [strings])
Attachments
(1 file, 2 obsolete files)
3.56 KB,
patch
|
mfinkle
:
review+
|
Details | Diff | Splinter Review |
Right now, there is no way to change, from inside Fennec, the type of keyboard that I want to use. It would be good if the user can choose different keyboards(input methods) from inside the Fennec browser. The way Android browser does it right now is to hold the tap on a text field to get a context menu, which gives you the option to choose your input method type. The way to test it right now is to use Swype on android.
Updated•14 years ago
|
tracking-fennec: --- → ?
Keywords: inputmethod
Updated•14 years ago
|
tracking-fennec: ? → 2.0b2+
Updated•14 years ago
|
Assignee: nobody → mbrubeck
Comment 1•14 years ago
|
||
Matt, we'll need a backend API to trigger the input method selection. Brad is looking/filing that
Updated•14 years ago
|
tracking-fennec: 2.0b2+ → 2.0+
Updated•14 years ago
|
Flags: in-litmus?
Updated•14 years ago
|
tracking-fennec: 2.0+ → 2.0b3+
Updated•14 years ago
|
Assignee | ||
Comment 3•14 years ago
|
||
Oops. I'm stealing, but I needed to test. This applies on top of the patch in bug 609696. It doesn't make this work for chrome textboxes, but I figured that can be done in bug 585875.
Assignee | ||
Comment 4•14 years ago
|
||
Updated to new input picker patch.
Attachment #488362 -
Attachment is obsolete: true
Comment 5•14 years ago
|
||
reassigned since Wes is patching
Assignee: mbrubeck → wjohnston
Whiteboard: [strings]
Comment 6•14 years ago
|
||
Comment on attachment 488924 [details] [diff] [review] Patch v2 >diff --git a/chrome/content/browser.xul b/chrome/content/browser.xul > <richlistbox id="context-commands" onclick="ContextHelper.hide();" flex="1"> > <richlistitem class="context-command" id="context-copy" type="copy" onclick="ContextCommands.copy();"> > <label value="©.label;"/> > </richlistitem> >+#ifdef ANDROID >+ <richlistitem class="context-command" id="context-select-input" type="textfield" onclick="ContextCommands.selectInput();"> >+ <label value="&inputMethod.label;"/> >+ </richlistitem> >+#endif id="context-inputmethod" type="input-text" When you unbitrot this patch, make sure this item ends up at the bottom of the context menu for textbox items >diff --git a/chrome/content/content.js b/chrome/content/content.js >+ if (elem instanceof HTMLInputElement && elem.mozIsTextField(true)) { >+ state.types.push("textfield"); >+ } Let not add this here. Instead just add "input-text" to the json.types here: http://hg.mozilla.org/mobile-browser/rev/e634cc4a8c35#l1.19 This was added by Brubeck's copy/paste patch >diff --git a/locales/en-US/chrome/browser.dtd b/locales/en-US/chrome/browser.dtd >+<!ENTITY inputMethod.label "Select Input Method"> >+ > <!ENTITY selectHelper.emptytext "Filter List"> >\ No newline at end of file Make sure we have blank lines at end of files r-, but close
Attachment #488924 -
Flags: review-
Assignee | ||
Comment 7•14 years ago
|
||
Adds this for chrome textboxes. Will try to do content in bug 611741.
Attachment #488924 -
Attachment is obsolete: true
Attachment #490153 -
Flags: review?(mark.finkle)
Updated•14 years ago
|
Attachment #490153 -
Flags: review?(mark.finkle) → review+
Comment 8•14 years ago
|
||
pushed: http://hg.mozilla.org/mobile-browser/rev/8c498f19a152
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 10•14 years ago
|
||
verified FIXED on build: Mozilla/5.0 (Android; Linux armv71; rv:2.0b8pre) Gecko/20101115 Namoroka/4.0b8pre Fennec/4.0b3pre
Status: RESOLVED → VERIFIED
Flags: in-testsuite?
Reporter | ||
Updated•14 years ago
|
Flags: in-litmus? → in-litmus?(ayanshah62)
Reporter | ||
Comment 11•14 years ago
|
||
https://litmus.mozilla.org/show_test.cgi?id=12692
Flags: in-litmus?(ayanshah62) → in-litmus+
You need to log in
before you can comment on or make changes to this bug.
Description
•