New issue
Advanced search Search tips

Issue 912012 link

Starred by 1 user
Status: Assigned
Owner:
dpa...@chromium.org
Cc:
nyerramilli@chromium.org
rbasuvula@chromium.org
dpa...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Focus does not travel on 'Relaunch' button on pressing tab key.

Project Member Reported by pranja...@virtusa.com, Dec 5 
Chrome Version:73.0.3630.0 (Official Build) 4e0c28599deef67a295ba4ecd2e0180a4b5157e0-refs/branch-heads/3630@{#1}(32/64 bit)

OS:  Win(7,8,8.1,10) , Mac(10.13.1 , 10.13.6 , 10.14.2) and Linux(14.04 LTS)OS 

What steps will reproduce the problem?
1.Launch chrome and navigate to 'Chrome://settings'.
2.Press tab key until focus reaches to 'Automatically send usage statistics....' and press enter key.
3.Now press tab key once and observe.

Actual  : Focus does not travel on 'Relaunch' button on pressing tab key.
Expected: Focus should be seen on 'Relaunch' button on pressing tab key.

This is a regression issue broken in ‘M-72’ and and soon update other bisect info,
Good Build: 72.0.3583.0
Bad Build : 72.0.3584.0
Actual Result.mp4
396 KB View Download
Expected Result.mp4
446 KB View Download

Comment 1 by pranja...@virtusa.com, Dec 5

Labels: hasbisect
Owner: se...@chromium.org
Status: Assigned (was: Unconfirmed)
Unable to provide bisect using per-revision script as it shows "We don't have enough builds error message" ,hence providing bisect using chromium bisect.

Chromium Bisect:
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/7e3361f0a1f2962a85c8cf36b6ea2f403328419e..177774d57a744b75630cba5507c3bf1ed419aea3	

Suspecting: https://chromium.googlesource.com/chromium/src/+/51ffa6364c24a0006f3e0de920091e6507549e9b

@Sébastien Séguin-Gagnon: Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Kindly review the attached screen-cast for reference.

Thank you.

Comment 2 by pranja...@virtusa.com, Dec 5 

Correction in Chrome version:

Chrome version:72.0.3626.7 (Official Build) Revision efcef9a3ecda02b2132af215116a03852d08b9cb-refs/branch-heads/3626@{#63}(32/64-bit)

Comment 3 by se...@chromium.org, Dec 5

Owner: dpa...@chromium.org
The change I made was to add more options in a dropdown in the payments page. I don't think it could cause this issue.

Not too sure how to help you triage either. Adding dpapad@ for his thoughts
►

Sign in to add a comment