Firefox after save card edit reverts to some other page

[TJoeT]

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 making a change to any card in lovelace and pressing save, HA pops to a different page. I think this has been a problem for many versions.

While I’m at it when trying to change the order of entities in the editor this hasn’t worked for a long time ether.

These are not problems in ms Edge.

Describe the behavior you expected

To stay on the same page after save button pressed.

The ability to drag entities into a new order.

Steps to reproduce the issue

1. edit a entities card and press save.

...

What version of Home Assistant Core has the issue?

2022.4.3

What was the last working version of Home Assistant Core?

I didn't track it. at least since 2021

In which browser are you experiencing the issue with?

Firefox

Which operating system are you using to run this browser?

windows 10 64bit

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

none

Additional information

No response

[liberty29]

I experience the same two issues on Linux Mint MATE, using the latest version of Firefox. Especially the inability to drag an item when editing a card can be annoying.

[ikey-ru]

It is not possible to change the order of objects in the editor Same issue on macOS in Firefox. Safari - no problem.

[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.

[steverep]

I experience this issue as well in 2022.8. It seems like history.back() is being fired because clicking forward in the browser brings me back to HA, although not in edit dashboard mode anymore.

@zsarnett do you know what may be going on here?

[prof7bit]

This has been happening for me since I started using home assistant half a year ago.

Sometimes if I open a fresh browser tab, load home assistant and then immediately begin editing the first tab on the default dashboard it does not happen. But after I have been clicking around a few times between different tabs or different dashboards and then try to edit something it will execute a history back when saving the edited card.

I am not exactly sure how to reproduce it in a reliable way, but if you tell me to show it to you it takes me no more than 30 seconds to trigger the bug.

1. Open a new tab in firefox
2. Load the home assistant front page / default dashboard
3. click around between a few dashboards in the sidebar
4. click around between a few tabs in one dashboard
5. click edit dashboard
6. click edit on a card
7. edit something (for example just the title or anything else) to make the save button appear
8. click save

If it does not trigger the bug then just repeat from step 3 onwards, maybe try editing a different card on a different dashboard, it won't take more than one or two tries until it triggers the bug and once it is in this state it will trigger the bug reliably on every save.

Extremely annoying.

[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.

[steverep]

Still an issue

[prof7bit]

Cancel will execute history.back() exactly one time, Save will execute it two times! Why? Why calling back() at all?

This can be observed when watching the forward arrow in the browser navigation becoming un-greyed after cancel, one click on browser-forward makes it grey again. When saving a card then it needs 2 clicks on forward to make it grey again.

Also a long press on the forward arrow (in firefox) shows the current position in the history being 2 steps before the end.

Question to the devs: Has anybody of the devs been able to reproduce this? Do you also see the effect of the browser being 2 steps back in the browsing history after clicking save? This problem is super annoying, I can't imagine there are only 4 people affected by this.

[helmuto-maker]

This is still an issue and has been for as long as I can remember (>1 year). Using Firefox.

[mill1000]

Still an issue for me with Frontend 20230705.1 and Firefox 115.0.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.

[prof7bit]

Latest version, still not solved.

[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.

[mill1000]

Pretty sure I still see this with the versions Core 2024.1.0 Frontend 20240103.3

[prof7bit]

I have seen this just yesterday, my version is always up to date, it happens pretty much every time when I edit my dashboards.

[helmuto-maker]

Same here - all versions of Home Assistant since forever. No matter if Firefox is on Windows or Linux.