Issue metadata
Sign in to add a comment
|
Regression: Cursor is not seen at 'First name' field of sign in overlay on second instance via tap/touch.
Reported by
jshan...@etouch.net,
Jul 5 2016
|
||||||||||||||||||||||
Issue descriptionChrome Version: 53.0.2785.6 (Official Build) dc1090fa0edd6091d6d99381c7ec40115c60327d-refs/branch-heads/2785@{#15}-32/64 bit OS: Windows 10(Touch device) Steps: 1. Launch Chrome, click on avtar icon and then click on Sign in to chrome button. 2. Select 'Create new account' from 'More option' menu via tap/touch, then tap on back button of sign in overlay. 3. Now again select 'Create new account' from 'More option' menu via tap/touch and observe. Actual: Cursor is not seen at 'First name' field on second instance after tap/touch on 'Create new account'. Expected: Cursor should be seen at 'First name' field on second instance after tap/touch on 'Create new account'. This is a regression issue broken in M-51, below is bisect info. Good build: 51.0.2671.0 Bad build: 51.0.2672.0 Narrow bisect: https://chromium.googlesource.com/chromium/src/+log/5241d81a41e319f8b1f4d9840cd8d1269b265788..9c64d516f6f9c9629391f940dc2d04608f770e06?pretty=fuller&n=100 Suspecting: r379968 ? Please help to re-assign if your change is not the cause for this issue Note: This is touch device specific issue, same works fine on mouse click.
,
Jul 5 2016
My CL r379968 only removed several layout tests and it shouldn't affect Chrome's behavior. Unfortunately I cannot narrow it down because I don't have a touch screen. anthonyvd@ can you take a look at this issue please? r379986 seems changed the sign-in modal. Thanks!
,
Oct 3 2016
Note: Above issue is reproducible on latest canary version: 55.0.2878.0
,
Dec 19 2016
--Chrome Identity automated triaging-- This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 18 2017
+msarda to figure out if this is still an issue.
,
Apr 20 2017
Not a P1 as it has been like this for a long time. Unfortunately, I do not have a Windows touch device either to see if I can reproduce it either.
,
Apr 19 2018
--Chrome Identity automated triaging-- This bug is Available and has gone one year without any activity. If another month passes without any activity, this bug will be closed out. Please provide an update with the latest status for this bug. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 11 2018
--Chrome Identity automated triaging-- This available, signin or profiles-related bug has gone at least 30 days since the last automated post without any further update. This bug will be closed out due to inactivity. Please re-open the bug and provide an update if it is still a valid or reproducible bug. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by jshan...@etouch.net
, Jul 5 2016Labels: Proj-Windows10