Closed
Bug 1278470
Opened 9 years ago
Closed 8 years ago
Typing in third party keyboard predictive typing ruins input
Categories
(Firefox for iOS :: General, defect, P1)
Tracking
()
VERIFIED
FIXED
Iteration:
1.27
People
(Reporter: Jamaicanboy63, Assigned: farhan)
References
Details
(Whiteboard: [MobileCore][ThirdPartyKeyboards])
Attachments
(1 file)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:46.0) Gecko/20100101 Firefox/46.0
Build ID: 20160502172042
Steps to reproduce:
So when i am typing using swiftkey in the search bar I can type in any thing for instance I type "Final" I see it in the predictive typing I tap the word I want it inputs "FFinal" it never use to do that for the past few updates.
Actual results:
Its adding an extra letter in that I confirm predictive typing
Expected results:
It should just have that one word with no extra letter when I type and use the predictive word.
Comment 1•9 years ago
|
||
This sounds like bug 1209052.
Updated•9 years ago
|
| Reporter | ||
Comment 2•9 years ago
|
||
(In reply to Aaron Train [:aaronmt] from comment #1)
> This sounds like bug 1209052.
It's a different issue from that one. Predictive typing just adds an extra letter of the first word you type.
Updated•9 years ago
|
tracking-fxios:
--- → ?
Updated•9 years ago
|
Comment 3•8 years ago
|
||
I can reproduce this issue in latest master using using GBoard, Swiftkey and Fleksy.
We should have this fixed before enabling by default the 3'rd party keyboard support.
Updated•8 years ago
|
Priority: -- → P3
Updated•8 years ago
|
Whiteboard: [MobileCore][ThirdPartyKeyboards]
| Assignee | ||
Comment 4•8 years ago
|
||
Attachment #8888873 -
Flags: review?(jdarcangelo)
Comment 5•8 years ago
|
||
Comment on attachment 8888873 [details] [review]
Pull Request
LGTM, but as I stated in the PR, it might not hurt to have someone else also look over this code who is more familiar with it since it seems to make significant changes.
Attachment #8888873 -
Flags: review?(jdarcangelo) → review+
| Assignee | ||
Comment 6•8 years ago
|
||
Agreed. I wish there was somebody who understood what was going on better. Our best bet is to give QA some time to do some testing with different keyboards.
| Assignee | ||
Updated•8 years ago
|
Assignee: nobody → fpatel
Iteration: --- → 1.26
Priority: P3 → P1
Whiteboard: [MobileCore][ThirdPartyKeyboards] → [MobileCore][ThirdPartyKeyboards][needsuplift]
| Assignee | ||
Comment 7•8 years ago
|
||
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•8 years ago
|
Whiteboard: [MobileCore][ThirdPartyKeyboards][needsuplift] → [MobileCore][ThirdPartyKeyboards]
Comment 9•8 years ago
|
||
Uplifted to v8.x
Updated•8 years ago
|
Updated•8 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 10•8 years ago
|
||
Reverted this patch in v8.x
Updated•8 years ago
|
Updated•8 years ago
|
Iteration: 1.26 → 1.27
| Assignee | ||
Comment 11•8 years ago
|
||
This should be fixed by
https://github.com/mozilla-mobile/firefox-ios/commit/b7d2697641fda38ee9851650f01fb62ad207adb5
The regressions created by the previous patch should also be fixed.
Status: REOPENED → RESOLVED
Closed: 8 years ago → 8 years ago
Resolution: --- → FIXED
Comment 12•8 years ago
|
||
Verifying as fix on master 529fb6a46.
| Assignee | ||
Updated•8 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•