1057852 - [Keyboard][Autocorrect] Autocorrect makes Here Maps & zMaps frustrating to use; corrects city names like "Orinda" to "Iring" and "Aptos" to "Soto's"

Status: RESOLVED INVALID

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

Description

[Daniel Holbert [:dholbert]]

STR:
 1. Install & open "Here Maps" or "zMaps" app from Marketplace
 2. Type in a city name or street name that's not recognized by autocorrect (examples below).
 3. Hit "return", "space", or "comma" keys on the keyboard (as if you were either done, or wanted to continue to type a zipcode or something)

ACTUAL RESULTS:
The thing you typed in gets autocorrected, in some cases to a completely different word.

EXPECTED RESULTS:
No autocompletion should happen. City/street names are weird enough that we shouldn't trust our autocompletion dictionary to know about them, or to be smart enough to know what the user wanted to type.  Moreover, mapping apps seem to be smart enough to handle some typos on their own, without needing them fixed in their text input fields.



EXAMPLES (from bay area city-names):
 Orinda gets corrected to "Iring"
 Moraga gets corrected to "Moorage"
 Aptos gets corrected to "Soto's"
 San Leandro gets corrected to "San Leandra"
 El Cerrito gets corrected to "El Ferrite" or "el ceTriton"

Also, the street label "Ter" (short for "Terrace") gets autocompleted to "Term".  I happen to live on a "terrace", so this frustrates me every time I use the app to navigate home. I can imagine that people living in cities like Orinda or Moraga would get pretty angry about having to fight with autocorrect every time they use the mapping app to find something local, too.

Comment 1

[Daniel Holbert [:dholbert]]

If apps have the capability to disable autocorrect in a text field, we should ask that major mapping / location-search apps enable this capability on their search fields.

Or, if such a capability doesn't exist, we should add it for cases like this.

I don't know exactly where this bug belongs, so I'm starting it in Gaia:Keyboard for now, in the hopes that this will get it on the radar of people who know about autocorrect.

VERSION INFO:
I'm running a Firefox OS 2.0 nightly build on my Flame device.

Comment 2

[Jan Jongboom [:janjongboom] (inactive)]

We have it already <input x-inputmode="verbatim" />

We can't fix this in platform.