Regression:[Devtools]Text does not get selected after bringing focus in filter textbox.
Reported by
pranjali...@etouch.net,
Oct 10
|
||
Issue descriptionChrome Version: 71.0.3575.0 (Official Build) e76b693f0dd0af3f866de220286b83a2847f0456-refs/branch-heads/3575@{#1}(32/64-bit) OS: Windows(7,8,8.1,10),Linux(14.04 LTS) and Mac(10.12.6, 10.13.1, 10.14.1, 10.13.6) What steps will reproduce the problem? 1.Launch Chrome and open devtools on NTP. 2.Go to console section and enter text in filter textbox. 3.Now press one tab key and press shift+tab key. 4.Observe. Actual Result: Text does not get selected after bringing focus in filter textbox of devtools. Expected Result: Text should get selected after bringing focus in filter textbox of devtools. This is regression issue broken in ‘M-63’ and soon update bisect info Good Build: 63.0.3223.0 Bad Build: 63.0.3225.0 You are probably looking for a change made after 504147 (known good), but no later than 504148 (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/b0d454706e1003638749bebb2b397f99b113fd80..a57d5aa65194cc780ab7039d97aa33d11c6d6585 Suspect: https://chromium.googlesource.com/chromium/src/+/a57d5aa65194cc780ab7039d97aa33d11c6d6585 @luoe: 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 refer attached screen cast. Thank You..!!
,
Oct 17
Thanks for the report. Since this is very low priority, and we don't have a great way to distinguish focus events originating from keyboard, marking as WontFix. |
||
►
Sign in to add a comment |
||
Comment 1 by pranjali...@etouch.net
, Oct 10