New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 781748 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: 2017-11-20
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression :focus does not travel to close icon on sign into chrome overlay.

Reported by pranjali...@etouch.net, Nov 6 2017

Issue description

Chrome Version:64.0.3260.0 (Official Build) eec83ceb16d47f70f5804a140687e268a6230b5c-refs/heads/master@{#514066}(32/64 bit)

OS:Windows (7,8,10),Linux (14.04 LTS),Mac(10.12.6,10.13.1).

Steps to reproduce:
1.Launch chrome and open NTP.
2.click on avatar icon and select 'sign into chrome' button. 
3.on overlay press tab key until focus reaches to close icon(X) and Observe.

Actual Result:Focus does not travel to close icon on sign into chrome overlay after pressing tab key.
Expected Result:Focus should be seen on close icon on sign into chrome overlay after pressing tab key.

This is Regression issue broken in 'M-63' and Using the per-revision bisect providing the bisect results,
Good Build:63.0.3223.0
Bad Build:63.0.3225.0

You are probably looking for a change made after 504421 (known good), but no later than 504422 (first known bad).

CHANGELOG URL:

The script might not always return single CL as suspect as some perf builds might get missing due to failure.

  https://chromium.googlesource.com/chromium/src/+log/1b62135c07abbd0fb531b03fddb3c2114cb06698..3131414035a033d1fb624913474dbdac04158198

Suspect:https://chromium.googlesource.com/chromium/src/+/3131414035a033d1fb624913474dbdac04158198


 
Actual_result.mp4
419 KB View Download
Expected_result.mp4
468 KB View Download

Comment 1 by ew...@chromium.org, Nov 10 2017

Cc: msarda@chromium.org
+Mihai as FYI

This is actually pretty high-priority, since we rely on users being able to get to the "x-to-close" button via the keyboard for a11y reasons. lfg@ - could you please take a look?

Comment 2 by lfg@chromium.org, Nov 10 2017

Cc: wjmaclean@chromium.org lfg@chromium.org
Components: Platform>Apps>BrowserTag
Labels: M-63
Owner: aval...@chromium.org
Alex, can you take a look? It looks like the element is getting focused, but the outer WebContents is not activated. I tried adding SetAsFocusedWebContentsIfNecessary in WebContentsViewChildFrame::TakeFocus, but it makes the behavior racy (works sometimes, but not always, so I assume there's some race between guest/embedder going on).

Cc: alex...@chromium.org

Comment 4 by avallee@google.com, Nov 15 2017

On this line:
https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/page/FocusController.cpp?type=cs&l=825

IsFocused() returns false.  SetFocusedFrame is called when the embedder renderer received the notification to advance focus from the oopif here: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/page/FocusController.cpp?type=cs&l=1120
Project Member

Comment 5 by bugdroid1@chromium.org, Nov 17 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/839ae6ef38f225cdf0195e186e9c162b26eadcd0

commit 839ae6ef38f225cdf0195e186e9c162b26eadcd0
Author: Alex Vallée <avallee@chromium.org>
Date: Fri Nov 17 19:23:16 2017

[chrome-signin] Reduce focus stealing.

With the OOPIF implementation of webview, the embedder page is not
considered focused when the guest has focus (it does not see any
keyboard input). This means that upon reaching the end of the
<webview>'s content and focusing an element in the embedder,
<paper-icon-button> in this case, the page is first refocused.

This event listener only seemed to expect this to happen once at the
beginning.

This CL prevents the authenticator from focusing the webview if another
element is focused when the page itself is focused.

The alternative would be to call focus only once, when constructing the
Authenticator.

Bug:  781748 
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Iac7020caad90c9e5e617f46bba392caeb09482b0
Reviewed-on: https://chromium-review.googlesource.com/775978
Commit-Queue: Alex Vallee <avallee@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#517511}
[modify] https://crrev.com/839ae6ef38f225cdf0195e186e9c162b26eadcd0/chrome/browser/resources/gaia_auth_host/authenticator.js

Status: Fixed (was: Assigned)
Labels: Merge-Request-63

Comment 8 by gov...@chromium.org, Nov 17 2017

NextAction: 2017-11-20
Change listed at #5 landed 88 mins back. Please update the bug on Monday morning with canary result. If change looks good in canary, I will approve the merge.

Note: If merge happens before 12:30 PM PT Monday, then we can pick it up for next week beta release. Thank you.
Project Member

Comment 9 by sheriffbot@chromium.org, Nov 18 2017

Labels: -Merge-Request-63 Merge-Review-63 Hotlist-Merge-Review
This bug requires manual review: M63 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), gkihumba@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: TE-Verified-M64 TE-Verified-64.0.3273.0
Rechecked the above issue on Windows (7,8,10),Linux (14.04 LTS),Mac(10.12.6)OS with latest canary chrome version :64.0.3273.0 and the issue is not reproducible.Kindly refer the attached screen cast for reference.
Actual_result.mov
1.4 MB Download
Labels: TE-Verified-64.0.3272.0
Rechecked the above issue on Windows (7,8,10) using build #64.0.3272.0 and Linux (14.04 LTS),Mac(10.12.6)OS using build #64.0.3273.0 and it is working fix as intended.
The NextAction date has arrived: 2017-11-20

Comment 13 by avallee@google.com, Nov 20 2017

Works fine on Mac canary with cross-process-guests enabled.
Labels: -Merge-Review-63 Merge-Approved-63
Approving merge to M63 branch 3239 based on comments #11, #13 and per offline chat with avallee@. Please merge ASAP. Thank you.
Project Member

Comment 15 by bugdroid1@chromium.org, Nov 20 2017

Labels: -merge-approved-63 merge-merged-3239
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/76df99b66c6e7b97c16ca9301645561de0abe68d

commit 76df99b66c6e7b97c16ca9301645561de0abe68d
Author: Alex Vallée <avallee@chromium.org>
Date: Mon Nov 20 16:30:41 2017

[M63][chrome-signin] Reduce focus stealing.

Merge to beta: M63.

With the OOPIF implementation of webview, the embedder page is not
considered focused when the guest has focus (it does not see any
keyboard input). This means that upon reaching the end of the
<webview>'s content and focusing an element in the embedder,
<paper-icon-button> in this case, the page is first refocused.

This event listener only seemed to expect this to happen once at the
beginning.

This CL prevents the authenticator from focusing the webview if another
element is focused when the page itself is focused.

The alternative would be to call focus only once, when constructing the
Authenticator.

Bug:  781748 
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Iac7020caad90c9e5e617f46bba392caeb09482b0
Reviewed-on: https://chromium-review.googlesource.com/775978
Commit-Queue: Alex Vallee <avallee@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#517511}(cherry picked from commit 839ae6ef38f225cdf0195e186e9c162b26eadcd0)
Reviewed-on: https://chromium-review.googlesource.com/777711
Reviewed-by: Alex Vallee <avallee@chromium.org>
Cr-Commit-Position: refs/branch-heads/3239@{#542}
Cr-Branched-From: adb61db19020ed8ecee5e91b1a0ea4c924ae2988-refs/heads/master@{#508578}
[modify] https://crrev.com/76df99b66c6e7b97c16ca9301645561de0abe68d/chrome/browser/resources/gaia_auth_host/authenticator.js

Labels: TE-Verified-M63 TE-Verified-63.0.3239.59
Rechecked the above issue on Windows (7,8,10),Linux (14.04 LTS),Mac(10.12.6)OS with latest canary chrome version :63.0.3239.59 and the issue is not reproducible.Kindly refer the attached screen cast for reference.
Actual_result.mov
1.8 MB Download

Sign in to add a comment