New issue
Advanced search Search tips

Issue 906592 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression : Pin pad is seen missing after clicking enabled 'On-Screen Keyboard' User and then on Pin lock enabled user In Multiple profile lock screen

Project Member Reported by mmanchala@chromium.org, Nov 19

Issue description

Chrome Version: 70.0.3538.110/11021.81.0 Stable-channel  Daisy,Kip and Reks
OS: Chrome

Pre-condition : Sign into 2 Users

What steps will reproduce the problem?
(1)In second User(Ex: B Account) and now enable Pin lock ->now Go to Uber tray -> click on user I'd and select 'Sign in to another user...' option for Multiple sign-in
(2)Now click on Uber tray and select 'Lock' option -> In Multiple login user lock screen -> observe for one User Pin pad is seen and another user 'Password' field is seen 
(3)Now click on User for which 'Password' field is seen  and click on Uber Tray and select 'Accessibility' -> now select 'On-Screen Keyboard' option
(4)click on  'On-Screen Keyboard' option such that keyboard will pop up > Now click on User for which Pin lock is enabled -> now observe Pin pad is seen missing 
(Please refer Video and Screenshot)


Expected: Pin pad should be available after clicking enabled 'On-Screen Keyboard' User and then on Pin lock enabled user
Actual: Instead Pin pad is seen missing 

This is Regression Issue as same is working fine on M-65

Note : Issue is also seen on M-66, M-67,M-68,M-69, M-71 and M-72

 
Actual_PinPadMissing.mp4
18.0 MB Download
Actual_PinPadMissing.jpg
461 KB View Download
Attaching Expected video for reference 
Expected_PinPad.mp4
18.9 MB Download
Cc: -alemate@chromium.org
Owner: alemate@chromium.org
alemate@ could you please triage?
Cc: alemate@chromium.org
Owner: jdufault@chromium.org
Jacob, you know this code better. Could you take a look?
Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment