Closed
Bug 860462
Opened 12 years ago
Closed 12 years ago
[Keyboard] add auto-correction UX
Categories
(Firefox OS Graveyard :: Gaia::Keyboard, defect)
Tracking
(blocking-b2g:-, b2g18+ fixed)
VERIFIED
FIXED
blocking-b2g | - |
People
(Reporter: djf, Assigned: djf)
References
Details
(Whiteboard: c=auto-correct)
Attachments
(3 files)
I'm creating this bug for the patch that enables auto-correction by hooking up the prediction engine to the keyboard. This is just one of many bugs auto-correct bugs under the umbrella of meta-bub 797170, however.
Assignee | ||
Comment 2•12 years ago
|
||
The patch is intended to enable autocorrect so we can have something to test and improve. There are lots of improvements still to be made to the back-end prediction engine. And there are probably UX improvements to be made as well. So this is just a start. Any auto-correction related bugs should be linked to the meta bug 797170.
Assignee | ||
Comment 3•12 years ago
|
||
Gregor, I've updated the patch to fix the bug you found and to change the misleading variable name.
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → dflanagan
Updated•12 years ago
|
Attachment #735945 -
Flags: review?(anygregor) → review+
Assignee | ||
Comment 4•12 years ago
|
||
Landed on master: https://github.com/mozilla-b2g/gaia/commit/132c5a712ec4d4e92208ba4fc65ca98b8be00b31
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 5•12 years ago
|
||
Hi, all, Thanks for your effort and help! I used following cases to verify this new feature/UX. (1) Disable word suggestion and auto correction. (2) Enable word suggestion but disable auto correction. (3) Enable word suggestion and auto correction. (4) Disable word suggestion but enable auto correction. As attach pictures, the new feature work as normal. I didn't find any side effect. Thanks! * Test build: (Mozilla-central-unagi/2013-04-14-03-06-04) - Mercurial-Information + Gecko revision="a3dad9390a30" + Gaia revision="288955e2758b" - Git-Information + Gecko revision="28701956b634c7bd9bb05f19533e4b744e9a9600" + Gaia revision="3fa788342953f33ab980fa1ba28deba1a1b8e650" By the way, if I find any auto correction problem, I will add comment to Bug 860550. Thanks! Have a nice day!
Status: RESOLVED → VERIFIED
Comment 6•12 years ago
|
||
Comment 7•12 years ago
|
||
Updated•12 years ago
|
QA Contact: whsu
Assignee | ||
Comment 8•12 years ago
|
||
Preemptively asking for leo+ all the bugs blocking the keyboard auto-correct umbrella bug 797170.
blocking-b2g: --- → leo?
Comment 9•12 years ago
|
||
seem like a product/UX decision whether we need auto-correct in 1.1
Flags: needinfo?(ffos-product)
Comment 10•12 years ago
|
||
Chris is driving keyboard improvement decisions.
Flags: needinfo?(ffos-product) → needinfo?(clee)
Comment 11•12 years ago
|
||
We should only land this once this has been reviewed by UX/Product/Engineering from a quality/consistency perspective. Can we land this on master and so we can have QA and others testing this first and then decide if we want to uplift to v1-train?
Flags: needinfo?(clee)
Comment 12•12 years ago
|
||
Hi, Chris, Actually, the feature has landed on master branch. I did a smoke test on this feature to make sure it doesn't make any side effect but not yet created test cases. Please refer to comment 5, comment 6, and comment 7. If we want to land this feature on v1-train, we may inform QAs to run full-run test on it. Thanks!
Comment 13•12 years ago
|
||
Per comment 11 and comment 12, requesting UX/Product/QA to review auto-correction quality/performance before deciding if this is good enough for 1.1.
Flags: needinfo?(jcarpenter)
Flags: needinfo?(jachen)
Flags: needinfo?(ffos-product)
Keywords: qawanted
Comment 14•12 years ago
|
||
The testing itself was already done in comment 5 to check if it was safe for uplift at a sanity level. comment 12 refers to adding test cases and doing more testing, which should not block an uplift.
Keywords: qawanted
Updated•12 years ago
|
Whiteboard: c=auto-correct
Comment 15•12 years ago
|
||
Altering NI to new FFOS UX address.
Flags: needinfo?(jcarpenter)
Flags: needinfo?(jachen)
Flags: needinfo?(firefoxos-ux-bugzilla)
Comment 16•12 years ago
|
||
Tracking since this change is wanted by UX but quality of fix needs to be assessed before decision to uplift. See below: On 5/7/13 12:03 AM, Christopher Lee wrote: Thanks Francis. Sounds like you and Josh are going to review the latest patches from David tomorrow and provide an assessment on the quality. I'm also going to get a build tomorrow and evaluate the latest changes and we can collectively make a call on if it's ready for uplift.
blocking-b2g: leo? → -
tracking-b2g18:
--- → +
Updated•12 years ago
|
Flags: needinfo?(ffos-product)
Updated•12 years ago
|
Flags: needinfo?(firefoxos-ux-bugzilla)
Comment 17•12 years ago
|
||
Assigning general FFOSUX needinfo to Francis, who is working on a collection of keyboard changes and improvements with Josh.
Flags: needinfo?(fdjabri)
Comment 18•12 years ago
|
||
This issue is has been fixed in master Gaia. But not uplifted in V1 train. Will this be uplifted in V1 train? Please comment.
Flags: needinfo?(dflanagan)
Assignee | ||
Comment 19•12 years ago
|
||
Leo: I would like to uplift it, but it is not my decision. Auto-correction is a new feature that has never been part of the plan for v1.1. The product and release managers will decide whether to uplift or not, I think. See the discussion in the parent bug 797170.
Flags: needinfo?(dflanagan)
Comment 20•11 years ago
|
||
Please add a testcase for this bug to moztrap for 1.1 testsuite. If yes, mark this in-moztrap+ when completed. If not, mark this in-moztrap-.
Flags: in-moztrap?
Updated•11 years ago
|
Flags: in-moztrap? → in-moztrap?(cschmoeckel)
Comment 22•11 years ago
|
||
Added Keyboard Suite Test Case #8501 - [Keyboard] Auto Correct's text prediction works correctly in the English Language & TC #8502 [Keyboard] Text prediction text entry in English keeps the capitalization entered by the user
Flags: in-moztrap?(cschmoeckel) → in-moztrap+
Updated•11 years ago
|
Flags: needinfo?(fdjabri)
You need to log in
before you can comment on or make changes to this bug.
Description
•