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

Focus is not automatically set on lovelace dashboard when selecting dashboard on app drawer which breaks shortcuts #13160

Closed
3 tasks done
DenisMir opened this issue Jul 10, 2022 · 4 comments
Labels

Comments

@DenisMir
Copy link

DenisMir commented Jul 10, 2022

Checklist

  • I have updated to the latest available Home Assistant version.
  • I have cleared the cache of my browser.
  • I have tried a different browser to see if it is related to my browser.

Describe the issue you are experiencing

The problem is that when selecting a dashboard in the app drawer the selected dashboard doesn't get the focus. This leads to a broken shortcut functionality. You have to manually click inside the content area to make the shortcuts work again.

Describe the behavior you expected

I'm selecting something from the app drawer on the left and can instantly call the shortcuts "e" and "c" without manually setting the focus to the right content area.
So from my point of view the shortcuts should be available from all panels. (as long as the focus is inside the homeassistant)

Steps to reproduce the issue

  1. Click on the left app panel and select e.g. a dashboard
  2. Try to immediately call a shortcut e.g. e which doesn't work
  3. Click in the right content area
  4. Retry calling the shortcut e and the shortcut works due to the manually set focus

What version of Home Assistant Core has the issue?

2022.7.2

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Google Chrome Version 103.0.5060.114 (Offizieller Build) (x86_64)

Which operating system are you using to run this browser?

macOS Monterey 12.4

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

I'd like to add that it would be useful to "namespace" the shortcuts like google mail does. So something like:

h + e -> Entities
h + c -> Commands

This is the same like Gmail does with g + i to go to the inbox.

This would easily allow even more shortcuts for navigating inside the frontend without having problems with duplicates from other stuff.

@github-actions
Copy link

github-actions bot commented Oct 8, 2022

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Oct 8, 2022
@DenisMir
Copy link
Author

DenisMir commented Oct 9, 2022

The problem still exists and is UX wise pretty annoying.

@github-actions github-actions bot removed the stale label Oct 9, 2022
@github-actions
Copy link

github-actions bot commented Jan 9, 2023

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jan 9, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 26, 2023
@DenisMir
Copy link
Author

The issue is still valid and should be open.

@github-actions github-actions bot locked and limited conversation to collaborators Mar 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant