Open
Bug 1250476
Opened 9 years ago
Updated 4 months ago
[Meta] Third-party keyboard compatibility
Categories
(Firefox for iOS :: General, defect)
Tracking
()
NEW
People
(Reporter: st3fan, Unassigned, NeedInfo)
References
(Blocks 1 open bug)
Details
(Keywords: meta, Whiteboard: [MobileCore][ThirdPartyKeyboards])
Here is some initial investigation for three popular keyboards:
Action Standard
New tab (empty)
Type 'sea' sea[rch.yahoo.com]
Backspace sea
Type 'r' sear[ch.yahoo.com'
Backspace 4x (empty)
Type 'foo bar' foo bar
Backspace 4x foo
backspace 3x (empty)
Type 's' s[earch.yahoo.com]
Type 'l' sl[ickdeals.com]
Action SwiftKey
New tab (empty)
Type 'sea' se[arch.yahoo.com]
Backspace s[earch.yahoo.com]
Type 'r' sr
Backspace 4x (empty)
Type 'foo bar' foo bar
Backspace 4x foo[dnetwork.com]
backspace 3x (empty)
Type 's' s[earch.yahoo.com]
Type 'l' sl[ickdeals.com]
Action Swype
New tab (empty)
Type 'sea' s[earch.yahoo.com]
Backspace (empty)
Type 'r' (fail bad state)
Backspace 4x (fail bad state)
Type 'foo bar' (fail bad state)
Backspace 4x (fail bad state)
backspace 3x (fail bad state)
Type 's' s[earch.yahoo.com]
Type 'l' s[earch.yahoo.com]
Action Fleksy
New tab (empty)
Type 'sea' sea[rch.yahoo.com]
Backspace se[arch.yahoo.com]
Type 'r' ser
Backspace 4x (empty)
Type 'foo bar' foo bar
Backspace 4x foo[dnetwork.com]
backspace 3x (empty)
Type 's' s[earch.yahoo.com]
Type 'l' sl[ickdeals.com]
| Reporter | ||
Updated•8 years ago
|
Whiteboard: [MobileCore][ThirdPartyKeyboards]
| Reporter | ||
Comment 1•8 years ago
|
||
Hi all,
I've spent some time re-testing the 3'rd party keyboards and the related existing bugs on latest master build. Here's a brief testing summary:
Keyboards used:
Swype
GBoard
Fleksy
SwiftKey
Go Keyboard
Scenarios tested:
Type "g" => see "google.com"
Type "g", hit backspace => see the URL empty
Type "go", hit backspace => see "g" and no autocompletion
Type "go", hit backspace, type "o" => see "google.com"
Type "Final", press predictive word "Final" => see "Final"
Type "go." => see "go."
Type "g", see "google.com", then tap the input field => the completion is accepted
Type "g", see "google.com", then hit "Go" => "google.com" is loaded in the current tab
Existing issues:
Bug 1194714 - URL bar text input misbehaves with Swype (and other third-party keyboards?)
I consider this to be a blocker
Bug 1278470 - Typing in third party keyboard predictive typing ruins input
This issue affects the use of predictive text in GBoard, Swiftkey and Fleksy and it would be nice to have it fixed. ATM, I'm not sure is if this should be considered a blocker.
Bug 1367006 - [Go keyboard] Imputed text gets duplicated when pressing on dot [.]
This is specific to Go Keyboard and should not be a blocker.
Bug 1209052 - URL autocomplete interferes with Swiftkey (and possibly other custom keyboards)
Wasn't able to reproduce it. I'll ask for more details from :sheppy
There's one other pretty bad issue with Fleksy. After starting Firefox, the keyboard is completely frozen/unusable for about 30 seconds. This happens only on phones. Safari/other apps are having the same issue, so I didn't file a bug.
| Reporter | ||
Updated•8 years ago
|
Summary: Third-party keyboard compatibility → [Meta] Third-party keyboard compatibility
Updated•3 years ago
|
Severity: normal → S3
Comment 2•2 years ago
|
||
The meta keyword is there, the bug doesn't depend on other bugs and there is no activity for 12 months.
:jeevans, maybe it's time to close this bug?
Flags: needinfo?(jeevans)
Comment 3•1 year ago
|
||
The meta keyword is there, the bug doesn't depend on other bugs and there is no activity for 12 months.
:jeevans, maybe it's time to close this bug?
Flags: needinfo?(jeevans)
Comment 4•4 months ago
|
||
The meta keyword is there, the bug doesn't depend on other bugs and there is no activity for 12 months.
:mreagan, maybe it's time to close this bug?
Flags: needinfo?(mreagan)
You need to log in
before you can comment on or make changes to this bug.
Description
•