Back arrow in entities list doesn't work after deleting an entity

[bdr99]

Checklist

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

Describe the issue you are experiencing

After deleting one or more entity from the entities list page, the back button needs to be pressed an additional number of times equal to the number of entities that were deleted. For example, if I delete 3 entities, the back button needs to be pressed 3 more times than usual in order to work.

Describe the behavior you expected

The back button should always work on the first try, regardless of whether an entity was deleted.

Steps to reproduce the issue

1. Navigate to Configuration -> Devices & Services -> Integrations.
2. Click on "# entities" for an integration that has entities that can be deleted.
3. Click one of the entities that can be deleted.
4. Click the red "delete" button at the bottom left of the entity dialog.
5. Click "OK" to confirm deleting the entity.
6. Repeat steps 3-5 as many times as desired.
7. Click the back arrow button at the top left of the entities list page, above the "Search entities" field. The button will not do anything the first "n" times it was clicked, where "n" is the number of entities that were deleted.

What version of Home Assistant Core has the issue?

2022.4.0

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Firefox 99.0

Which operating system are you using to run this browser?

Windows 11 21H2

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

[github-actions[bot]]

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.

[bdr99]

This is still an issue in HA 2022.7.

[github-actions[bot]]

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.

[bdr99]

This issue still exists in HA 2022.10.1.

[github-actions[bot]]

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.

[bdr99]

Issue still exists in HA 2023.11.2.

[github-actions[bot]]

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.

[bdr99]

Issue still exists in HA 2024.2.1. In fact, I just realized you don't even need to actually delete the entity in order to trigger the issue. Just getting to the entity deletion confirmation dialog, then tapping outside of it to exit it, is enough to trigger the issue.

[github-actions[bot]]

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.

[bdr99]

Issue still exists in HA 2024.5.4.

[github-actions[bot]]

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.

[bdr99]

Issue still exists in HA 2024.8.2.

[github-actions[bot]]

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.