-
Notifications
You must be signed in to change notification settings - Fork 30.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debug Hover: Allow keyboard to search through properties #127716
Comments
@jasonwilliams good catch, thanks for opening this issue. Now we support that you can click in the debug hover and type the name of the variables to be navigated to them. This already works in the variables view. To verify: open debug hover, click on it, start typing the name of the variable from the hover and make sure that variable gets focused |
I agree, my expectation would be moving towards the target but keeping the hover window the same size |
@jasonwilliams yeah that is the default behaviour |
@isidorn can you go straight to top straight to bottom via the keyboard? (Sorry this may need to be a separate request if not) |
@jasonwilliams is the rest of the implementation working ok right now? |
I can verify |
I won’t be at my machine for a few days so would need to delegate verifying to @connor4312 |
@jasonwilliams yeah, |
When hovering over an object (while the breakpoint is triggered) you can get a list of properties. Sometimes that list is very long. Is it possible to have a similar experience to the Explorer (in the side bar), where typing a letter moves the focus to that property?
For example in the gif below i would expect to type "me" and be taken down to "memoizedProps"

When the hover has focus the keyboard doesn't change content in the editor anyway so this should be safe to add without changing people's workflow.
The text was updated successfully, but these errors were encountered: