Regression:Unnecessary chrome browser get relaunch after pressing tab key on chrome://flags page.
Reported by
pranjali...@etouch.net,
Dec 20 2017
|
||||
Issue descriptionChrome Version: 64.0.3282.39 (Official Build) 685da0f069900495038d4dae4c1d7ac4bf489a47-refs/branch-heads/3282@{#286} OS:Mac(10.12.6,10.13.2),Win(7,8,10),Linux(14.04 LTS) Test URL:https://chrome.google.com/webstore/detail/go-back-with-backspace/eekailopagacbcdloonjhbiecobagjci/reviews Steps to reproduce: 1.Launch Chrome and navigate to chrome://flags. 2.Press tab key until focus reaches to last flag ,again press tab key and then press spacebar key 3.observe. Actual Result:Unnecessary chrome browser get relaunch after pressing tab key on chrome://flags page. Expected Result:Chrome browser should not relaunch after pressing tab key on chrome://flags page. This is a regression issue, broken in M-63 series, Using the per-revision bisect providing the bisect results, Good Build:63.0.3238.0 Bad Build:63.0.3239.0 You are probably looking for a change made after 508285 (known good), but no later than 508286 (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/9d39e939e54ce0106cf0d36655faf7881062342e..0fc5451ac52eac5f141b72af906cb794baa1699b Suspect:https://chromium.googlesource.com/chromium/src/+/0fc5451ac52eac5f141b72af906cb794baa1699b edwardjung@:Kindly help to reassign, if your changes are not related to this issue.
,
Dec 20 2017
,
Dec 20 2017
As this is a developer page, I don't think it's a big worry that someone is going to tab through all the flags. It's unlikely they will be pressing space without seeing a focus point.
,
Jan 9 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by ranjitkan@chromium.org
, Dec 20 2017Labels: -M-65 M-63