Closed Bug 847858 Opened 12 years ago Closed 7 years ago

SIM PIN Lock screen improving.

Categories

(Firefox OS Graveyard :: Gaia::System::Lockscreen, defect)

Other
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: nhsieh, Unassigned)

References

Details

Attachments

(3 files)

Attached image SIM Lock screen
SW Build number: 20130228070201 Component/s: SIM Lock Detailed Steps to Reproduce the Issue: 1.Insert an SIM card 2.Power on the device and wait into idle screen 3.Press settings -> SIM security 4.Press Enable button -> Enter SIM PIN 5.Reboot device 6.Unlock screen 7.Enter SIM lock screen Actual Behavior: No emergency call button and any hint for user. Keypad has dot button and it's not working. Expected Behavior: 1. The screen has emergency call button and hint at first like "3 retries left". 2. step 4. Keypad without dot button 3. Cursor in input area is needed.
Visual Guidance for Keypad, textfield and spacing.
^ Design Approved ^
In the new version there is no return button? What if I hit a know number and I want to correct it?
Assignee: nobody → mihai
Hi Przemek, a PIN specific keyboard layout (with only digit keys) was introduced by the patch for bug 820268, however that layout has an empty key (see attachment 734218 [details]). Should that empty key be 'EMERGENCY CALL' or 'ENTER'? Moreover, can you also address comment 3? Thanks!
Flags: needinfo?(pabratowski)
Sorry for the delay, I suggest we remove the empty key and add a cursor into the input area.
Flags: needinfo?(pabratowski)
(In reply to Przemek Abratowski [:przemek] UX from comment #6) > Sorry for the delay, I suggest we remove the empty key and add a cursor into > the input area. What do you mean by "add a cursor into the input area"? Do you mean that the delete key should be included in the input area like in the dialer screen? Would be great if you could simply update your visual guidance attachment (comment 1) with the changes wanted to the current PIN keyboard. Thanks!
Flags: needinfo?(pabratowski)
Attached image Visual Guidance
Empty key bottom left, and place a cursor in the first input field to start.
Flags: needinfo?(pabratowski)
(In reply to Przemek Abratowski [:przemek] UX from comment #8) > Created attachment 775688 [details] > Visual Guidance > > Empty key bottom left, and place a cursor in the first input field to start. Hi Przemek, thanks for the visual guidance screenshot, however that is suitable for the lockscreen passcode entry (4 digits) and not for the SIM PIN entry (which can be between 4 to 8 digits long). This bug highlights the missing "Emergency call" button in the PIN keyboard (point 1. from expected behavior in description) and a couple of other issues which are not reproducible anymore. So the big question(s) would be: 1. What should the bottom row of buttons be for the PIN keyboard? 2. Should the keyboard look like the one in the dialer -- with character sub-labels for digits (i.e. 'ABC' under key 2, as your visual guidance shows), or as it currently is -- without any sub-labels for digit keys (check attachment 734218 [details])?
Flags: needinfo?(pabratowski)
The initial intent of the visual guidance was to make all the number pads look similar, so that's why I'm asking that we make the PIN keyboard look like the dialer. Why can't the bottom row look like the keyboard in attachment 775688 [details]?
Flags: needinfo?(pabratowski)
On the SIM PIN keyboard generaly at the GSM phone the # key meaning end of data (OK key) but the # key is missing from the sreen
I've asked (In reply to Andras FEHER from comment #11) > On the SIM PIN keyboard > generaly at the GSM phone the # key meaning end of data (OK key) > but the # key is missing from the sreen Android doesn't have this #key at the PIN code keyboard. Our layout is set a space (nothing) key at the position, but I don't know whether this is a bug or feature (Android have a "Cancel" key at the same position). And I found that they're these two keypads are the same on the new build now. So can we close this bug?
Flags: needinfo?(firefoxos-ux-bugzilla)
Rob is the UX owner for Lockscreen. He can talk about the intended design as well as any forthcoming changes. Rob, also feel free to flag Casey as needed on visual aspects of the Lockscreen refresh for 1.4, if there are any changes to what Przemek stated earlier.
Flags: needinfo?(firefoxos-ux-bugzilla)
Depends on: 951526
Assignee: mihai → nobody
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: