Closed Bug 935495 Opened 11 years ago Closed 10 years ago

[first run] don't use word suggestion/spell check/autocorrection for password input to connect to hidden Wi-Fi network

Categories

(Firefox OS Graveyard :: Gaia::First Time Experience, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(tracking-b2g:backlog)

RESOLVED FIXED
2.1 S7 (24Oct)
tracking-b2g backlog

People

(Reporter: aryx, Assigned: sfoster)

References

Details

(Whiteboard: [systemsfe])

Attachments

(1 file)

Boot2Gecko 1.2.0.0-prerelease 20131104224010 on Keon, update channel 'default'

Similar to bug 825061.

When connecting to a hidden Wi-Fi network with WPA-PSK, the password input gets spellchecked.
Seems this was fixed at some point.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Reopening. After resetting my Keon (Boot2Gecko 2.2.0.0-prerelease 20141009012329) and trying to join a hidden network in the FTU, autocorrection changes the input in the password field.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
We should fix this. Can we check 2.1? Seems like a potential blocker if it is affected.
Keywords: qaurgent
Also happens with 2.1.0.0 20141009000203 on Flame KK.
Keywords: qaurgent
Apologies for the fire-drill, I was in the middle or something and not able to check on what sounded like a potentially serious issue. Having looked at this, this is a bit annoying only: the suggestions arent applicable when entering a password. Nothing is actually replaced from under the user, you just keep typing and ignore the suggestions.

The input in question toggles between 'text' and 'password' type based on the 'show password' checkbox. When its a password type, you get no suggestions. When its a text type, you do. We need to provide a hint to the keyboard app to not show this stuff, but my initial naive efforts using autocomplete="off" did nothing. I'll keep an eye out and ask around for how to accomplish this. Putting it on the backlog meantime.
Whiteboard: backlog
> Nothing is actually replaced from under the user, you just keep typing and ignore the suggestions.
Looking at the bug summary, I might have expressed the issue not clearly enough: While showing the password and typing, if autocorrection is enabled, the input will get autocorrected.

Steps to reproduce:
1. Enable autocorrection (is enabled by default in production builds on some devices).
2. Set language to English (US) and also use the English keyboard.
3. Go to Settings > Wi-Fi > Manage Networks > Join Hidden Network.
4. Toggle the checkbox to show the password
4. In the password field, type "hairi mo "
Actual result:
Password field contains "Haiti mob "

Expected result:
Password field contains "hairi mo "
Summary: [first run] don't use word suggestion/spell check for password input to connect to hidden Wi-Fi network → [first run] don't use word suggestion/spell check/autocorrection for password input to connect to hidden Wi-Fi network
Ok noted, I'm adding systemsfe for consideration as a blocker
Whiteboard: backlog → backlog [systemsfe]
[Blocking Requested - why for this release]: Bad UX, password gets autocorrected when trying to connect to hidden network
blocking-b2g: --- → 2.1?
Whiteboard: backlog [systemsfe] → [systemsfe]
Being that this has been there for 1 year+, it seems unlikely that we'd block on this for the last day of FC. Something we should definitely fix though. Maybe we can request uplift on it?
I agree with Kevin. Definitely priority to fix but its not a blocker. Lets go the uplift approval way and decide based on the risk.
blocking-b2g: 2.1? → backlog
Priority: -- → P1
Ah ha. From  the #wifi_password field in the same file (apps/ftu/index.html) it seems we need x-inputmode="verbatim" on #hidden-wifi-password
Working on this + marionette test
Assignee: nobody → sfoster
Target Milestone: --- → 2.1 S7 (24Oct)
Depends on: 1084186
Adds a-inputmode="verbatim" on the hidden network password field as our current/only mechanism to disable autocorrect in a text field. 

In the marionette test, I tried testing the actual autocorrect behavior with sendKeys and waits in the test, but although you can watch the keyboard show and the suggestions list populate, we dont get the same autocorrecting behavior as on device. So the test just asserts that x-inputmode has value verbatim for now.

Note that bug 1084186 tracks the issue that x-inputmode=verbatim is really a workaround for turning off autocorrect. If we get other options from the platform, we'll want to revisit this.
Attachment #8507215 - Flags: review?(fernando.campo)
Comment on attachment 8507215 [details] [review]
Add x-inputmode=verbatim to avoid autocorrecting password

Although I wasn't able to repro on current master (so it might have been fixed at some point), adding verbatim to inputmode it's the way it should be, so glad we're adding it.

Just added a comment for a minor style nit, thanks Sam.
Attachment #8507215 - Flags: review?(fernando.campo) → review+
Merged to master: https://github.com/mozilla-b2g/gaia/commit/ac73ec022b29b835c4a27d13d08c32acedf8c57d
Commit: https://github.com/mozilla-b2g/gaia/commit/e14b283312eb81305afcae5020971963329b79da

:fcampo: I got the wifi_test change in there you noted to keep the HTML the same. I'd rather do any batch id convention renaming in a separate bug. That particular one I touched because it duplicated another element with the same id, and produced initially-puzzling results when I was trying to write a marionette test for it
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
(In reply to Sam Foster [:sfoster] from comment #15)
> :fcampo: I got the wifi_test change in there you noted to keep the HTML the
> same. 
Thanks :)
> I'd rather do any batch id convention renaming in a separate bug. 
+1
blocking-b2g: backlog → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: