Focus lost after adding watch
Reported by
edw...@breyfamily.net,
Nov 29
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36 Steps to reproduce the problem: 1. From Developer Tools > Watches, add the watch "['a','b']". 2. Press the RightArray key. What is the expected behavior? The mapping of keys to values is shown: 0: "a" 1: "b" length: 2 __proto__: Array(0) What went wrong? After the new watch was added, it should have received focus, but didn't. If it had focus, the RightArrow key would expand the tree to show the children (array elements in this case). Did this work before? No Chrome version: 70.0.3538.110 Channel: stable OS Version: 10.0 Flash Version:
,
Nov 30
Thanks for filing the issue... Unable to reproduce the issue on reported chrome version 70.0.3538.110 using Windows 10. Steps: --------- 1. Launched reported chrome 2. Opened Dev tools >> Sources > Watch 3. Clicked on + and Added the watch ['a','b'] and clicked on the RightArray key. As we have observed that watch displaying as expected @Reporter: Request you to retry this issue with fresh profile without any extensions & apps or reset all the flags and verify this on chrome beta 71.0.3578.75, you can download latest chrome builds here:" https://www.chromium.org/getting-involved/dev-channel ". Let us know whether issue still persists. Thanks..!
,
Nov 30
Step 2 of my repro is "Press the RightArray key". That means press the RightArrow key on the keyboard. You wrote, "clicked on the RightArray key". It sounds like you used the mouse to click the arrow on the screen. Using the mouse works for me, too. The problem is with keyboard support. After typing in a watch, it's common to want to expand its results right away. Your hands are already on the keyboard, so it's efficient and ergonomic after pressing Enter to add the watch to press the RightArrow key to expand its results, rather than reach for the mouse. It looks like the Developer Tools were built with keyboard support in mind, but it's not working in this scenario.
,
Nov 30
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 4
Joel, could you please take a look.
,
Dec 4
It looks like the complaint is that the watches pane is not keyboard navigable. Seems to be related to the console keyboard navigation effort. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by viswa.karala@chromium.org
, Nov 30