New issue
Advanced search Search tips

Issue 615984 link

Starred by 3 users

Issue metadata

Status: Available
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression: Weird behavior of focus highlight is seen for sign in overlay on tap/touch.

Reported by jshan...@etouch.net, May 31 2016

Issue description

Chrome Version: 52.0.2743.19 (Official Build)Revision b25ac237c4e0eee088839ade87facf7b04ee3a16-refs/branch-heads/2743@{#129}(32/64-bit)
OS: Windows 10(Touch device)

Pre-condition: 'Enable new gaia password-separated sign in flow' from chrome://flags

Steps:
1. Launch chrome, go to chrome://settings, click on Sign in to chrome button.
2. Press ‘tab’ key until focus reaches ‘Close’(X) icon and then tap/touch on 'Next' button.
3. Observe at ‘Close’(X) icon.

Actual:Unnecessary focus highlight stays at ‘Close’(X) icon even after tap/touch on 'Next' button.

Expected: No focus highlight should be seen at ‘Close’(X) icon after tap/touch on 'Next' button.

This is regression issue,broken in ‘M 51’ and below is narrow bisect:
https://chromium.googlesource.com/chromium/src/+log/5241d81a41e319f8b1f4d9840cd8d1269b265788..61f3f4f037aca857735769cda129e18e38e8853e?pretty=fuller&n=100

Suspecting: r379986 ?

Good build: 51.0.2670.0
Bad build: 51.0.2672.0

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.
 
 
Actual_result.mp4
428 KB Download
Project Member

Comment 1 by sheriffbot@chromium.org, Jun 1 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 2 by sheriffbot@chromium.org, Jul 7 2016

Labels: -M-53 -Pri-1 M-54 MovedFrom-53 Pri-2
This issue is Pri-1 but has already been moved once. Lowering the priority and moving to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -M-54 M-55
Note: Above issue is still reproducible on latest canary version 55.0.2878.0
Project Member

Comment 4 by sheriffbot@chromium.org, Dec 19 2016

Status: Available (was: Assigned)
--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
Owner: msarda@chromium.org
+msarda since I no longer work on Identity.
Cc: -ashej...@chromium.org
Status: Assigned (was: Available)
Project Member

Comment 8 by sheriffbot@chromium.org, Sep 3

Status: Available (was: Assigned)
--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

Sign in to add a comment