Closed Bug 824929 Opened 12 years ago Closed 11 years ago

[SIM screen] The Done key is always active and can be pressed before the PIN Code is introduced

Categories

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

x86_64
Windows 7
defect
Not set
normal

Tracking

(b2g-v1.2 fixed, b2g-v1.3 fixed)

VERIFIED FIXED
1.2 C3(Oct25)
Tracking Status
b2g-v1.2 --- fixed
b2g-v1.3 --- fixed

People

(Reporter: isabelrios, Assigned: fcampo)

Details

(Whiteboard: testrun 5.1, burirun2)

Attachments

(2 files)

Unagi Test Run 1
Gaia 16006ea
Geck cb6ee76
PROCEDURE
 1. Turn on the device using a SIM Card with PIN
 2. Before introducing the PIN Code, click on Done key

EXPECTED
 Done key should be disabled until user introduces the PIN Code

ACTUAL
 The Done key can be clicked with no PIN inserted. The behaviour of this key is the same no matter if the PIN has been introduced
Right now we have a check on length of the pin input when pressing Done, but being always enabled is part of the code.

Asking UX for confirmation about the expected behaviour.
Flags: needinfo?(vpg)
Agree with Isabel, it should be disabeled until reaching the mimimum of characters accepted to confirm if the pin is valid.
Flags: needinfo?(vpg)
how do we make the user aware of the reason why the button is disabled? Add the information (PIN code must be between 4 and 8 characters) to the input label? Show the error till the minimum is reached?

Should we disable the button also if the max number (8) is reached? Or just not let the user to write more than 8 on the input field?
Testrun 5.1. Test case  #5046
Whiteboard: testrun 5.1
Also seen on the Buri 1.2 mozilla RIL.  The Send button is enabled despite nothing in the textbox.

Build ID: 20131003004003
Gecko: http://hg.mozilla.org/releases/mozilla-aurora/rev/7dfe4a775531
Gaia: 9e21b6bea92fdafcb6787120a8cde0eb25a50495
Platform Version: 26.0a2
Whiteboard: testrun 5.1 → testrun 5.1, burirun2
This fell out of the radar completely, I see questions unanswered, so I'll try to give it a spin
Assignee: nobody → fernando.campo
Comment on attachment 814126 [details] [review]
Link to PR - https://github.com/mozilla-b2g/gaia/pull/12710

provided the last nit on GH is solved
Attachment #814126 - Flags: review?(jmcf) → review+
merged on master https://github.com/mozilla-b2g/gaia/commit/907a8656e49599d334203c22dcbdb3f98c1d7864

Thanks for the review. Asking for approval v1.2
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Attachment mime type: text/plain → text/x-github-pull-request
Target Milestone: --- → 1.2 C3(Oct25)
NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.

[Approval Request Comment]
[Bug caused by] (feature/regressing bug #):
[User impact] if declined: user will be able to press Done button without a pin introduced, and then see an error message. We can avoid this with the patch.
[Testing completed]:
[Risk to taking this patch] (and alternatives if risky): low risk, mostly a visual change
[String changes made]:
Attachment #818982 - Flags: approval-gaia-v1.2?
Attachment #818982 - Flags: approval-gaia-v1.2? → approval-gaia-v1.2+
Hi John,

how should we proceed in order to uplift this patch to 1.2 branch?. Thanks!
Flags: needinfo?(jhford)
[v1.2 94c8d4f] Merge pull request #12710 from fcampo/ftu-doneButton-824929
Flags: needinfo?(jhford)
Verified on 10/29 v1.2 build:
Gecko-76298d3
Gaia-2ad6152
Status: RESOLVED → VERIFIED
Uplifted 907a8656e49599d334203c22dcbdb3f98c1d7864 to:
v1.3 already had this commit
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: