Closed Bug 851314 Opened 12 years ago Closed 12 years ago

Text prediction doesn't take into account the first letter of the word if it's uppercase

Categories

(Firefox OS Graveyard :: Gaia::Keyboard, defect)

All
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:-, b2g18 fixed)

RESOLVED FIXED
blocking-b2g -
Tracking Status
b2g18 --- fixed

People

(Reporter: stas, Assigned: ckerschb)

References

Details

Attachments

(1 file)

I'm testing the new text prediction engine that landed in bug 838227 and I notice that it does't take into account the first latter of the word if it's typed in uppercase. See the following two example of my trying to type "hello" and "Hello". h -> his he had he -> he Henry Head hel -> held help helps hell -> hello hell held H -> the to this He -> early end each Hel -> election elected elements Hell -> elliptical ellipse ellipsoid
Assignee: nobody → mozilla
Attached patch pull request (deleted) — Splinter Review
Attachment #725259 - Flags: review?(anygregor)
Attachment #725259 - Flags: review?(anygregor) → review+
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Shouldn't the code responsible for inserting the predicted word capitalize it if the original word typed by the user was capitalized too?
(In reply to Staś Małolepszy :stas from comment #4) > Shouldn't the code responsible for inserting the predicted word capitalize > it if the original word typed by the user was capitalized too? Yes, if the user explicitly selected it or maybe if we are at the beginning of a sentence. I don't think this should be part of the prediction engine itself. The code that inserts the word should take care of it.
(In reply to Gregor Wagner [:gwagner] from comment #5) > (In reply to Staś Małolepszy :stas from comment #4) > > Shouldn't the code responsible for inserting the predicted word capitalize > > it if the original word typed by the user was capitalized too? > > Yes, if the user explicitly selected it or maybe if we are at the beginning > of a sentence. > I don't think this should be part of the prediction engine itself. The code > that inserts the word should take care of it. I filed bug 851565.
Comment on attachment 725259 [details] [diff] [review] pull request This needs to be uplifted along with the DAG work.
Attachment #725259 - Flags: approval-gaia-v1+
Marking as blocking tef? and requesting uplift.
blocking-b2g: --- → tef?
I was not able to uplift this bug to v1-train. If this bug has dependencies which are not marked in this bug, please comment on this bug. If this bug depends on patches that aren't approved for v1-train, we need to re-evaluate the approval. Otherwise, if this is just a merge conflict, you might be able to resolve it with: git checkout v1-train git cherry-pick -x -m1 0e9009b66f21c2b92bc37ef3f096fe385c4d70de <RESOLVE MERGE CONFLICTS> git commit
Flags: needinfo?(mozilla)
tef- as bug 838227 has been also marked as tef-
blocking-b2g: tef? → -
Uplifted commit 0e9009b66f21c2b92bc37ef3f096fe385c4d70de as: v1-train: c00268805104809619e4fec22021db6ffb19a2d3
I guess I was not in charge of uplifting this anyway - clearing the needinfo flag!
Flags: needinfo?(mozilla)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: