Skip to content
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

Better keyboard navigation & devtools consistency #1537

Closed
kangax opened this issue Mar 23, 2021 · 11 comments
Closed

Better keyboard navigation & devtools consistency #1537

kangax opened this issue Mar 23, 2021 · 11 comments

Comments

@kangax
Copy link

kangax commented Mar 23, 2021

Is your feature request related to a problem? Please describe.

The recently added keyboard navigation in the components inspector is great but is often hard to work with because it doesn't follow the behavior of devtools that many developers are used to. Not only is it inconsistent but it also lacks functionality that makes it easy to navigate to the parent with one keypress in chunks of trees with many children.

Describe the solution you'd like

To mimic devtools behavior:

  • in collapsed view right arrow should expand the element (this is implemented)
  • in expanded view left arrow should collapse the element (this is implemented)
  • in expanded view right arrow should jump to the first child
  • in collapsed view left arrow should jump to the parent

Note that both Chrome and Firefox have the same behavior.

@nummi
Copy link
Collaborator

nummi commented Mar 24, 2021

@kangax Thanks for the feedback. Would you be interested in submitting a PR for this?

@kangax
Copy link
Author

kangax commented Mar 24, 2021

@nummi I'd love to look into this but unsure I'll have much time in the near future. I'll post here if something changes.

@RobbieTheWagner
Copy link
Member

@kangax happy to help if you have questions on this. Would love to get a PR going!

@geneukum
Copy link
Contributor

geneukum commented Apr 4, 2022

Hey! I’d like to contribute to this project and this seems like a good first issue to tackle.

Does anyone mind if I assign this to myself?

@kangax
Copy link
Author

kangax commented Apr 4, 2022 via email

@geneukum
Copy link
Contributor

geneukum commented Apr 8, 2022

OK, I opened up a PR with a first cut at the changes here: #1959.

I'm definitely happy to make any modifications that are desirable to get this integrated. Thanks all!!

@RobbieTheWagner
Copy link
Member

@geneukum since your PR is merged, should this be closed now?

@geneukum
Copy link
Contributor

@rwwagner90, I think that this could be closed out, but it might be nice just to have @kangax sanity check the changes just to make sure that the updated keybindings work as expected?

@kangax
Copy link
Author

kangax commented Apr 21, 2022

@geneukum I can check but not sure if master was cut into a release yet?

@geneukum
Copy link
Contributor

@kangax Ah, yeah, it doesn't look like it. I think that you'd need to build from source and then install that in order to be able to test these changes out.

I understand that's definitely a bit more involved though... We could always just close this issue out and then file a separate issue if there are any additional desired changes in the future.

@RobbieTheWagner
Copy link
Member

Closing this issue for now. Will try to get a release out soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants