Issue metadata
Sign in to add a comment
|
Regression:[Settings]Focus highlight does not travel on site settings entries on second instance.
Reported by
pranjali...@etouch.net,
Oct 19
|
||||||||||||||||||||||||
Issue descriptionChrome Version: 72.0.3585.0 (Official Build) 2eea43d10d3448c382da58fa116d4391f0d9db6d-refs/branch-heads/3585@{#1}(32/64 bit) OS: Win(7,8,8.1,10) , Mac(10.13.1 , 10.13.6 , 10.14.1) and Linux(14.04 LTS) Precondition: 1)Enable 'Site settings' flag from 'chrome://flags'. 2)Atleast one entry should be present in 'chrome://settings/content/all'. What steps will reproduce the problem? 1.Launch chrome and navigate to 'chrome://settings/content/all'. 2.Press tab key until focus reaches to site setting entries. 3.Repeat step 2 and observe. Actual : Focus highlight does not travel on site settings entries on second instance. Expected: Focus highlight should travel on site settings entries every time. This is Regression issue seen in M-72, and will soon update other info. Good Build: 72.0.3583.0 Bad Build: 72.0.3584.0 Chromium bisect info: You are probably looking for a change made after 600223 (known good), but no later than 600228 (first known bad). CHANGE-LOG URL: https://chromium.googlesource.com/chromium/src/+log/62f2f8f209a82db0dd5a311eb4f844bddb75c98e..631a939b2b9a02a05cd1db367c7ea7fb17d14f50 Suspecting: https://chromium.googlesource.com/chromium/src/+/177774d57a744b75630cba5507c3bf1ed419aea3 @dpapad: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner. Note:Tried per revision bisect on Windows ,Mac and Linux OS but unable to perform the same since getting "RuntimeError: We don't have enough builds to bisect" error Thank You |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dpa...@chromium.org
, Oct 23Status: Duplicate (was: Assigned)