Prevent leaving the editor if there are unsaved changes

[jpbede]

Proposed change

Prevent (accidentally) exiting the automation/script/scene editor by navigating in the sidebar if you have unsaved changes. You will now be asked if you are sure you want to leave the editor.

WTH: https://community.home-assistant.io/t/wth-doesnt-ha-ask-if-i-want-to-save-automations/804030

Bildschirmaufnahme.2024-12-05.um.19.50.50.mov

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue or discussion:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

[silamon]

There's a similar PR here: #20161

[bramkragten]

I like it! Nice work!

[silamon]

Tested, works pretty solid.

[bramkragten]

There are a few cases that are not handled by this solution, as it only works for anchor links. Like if you open the more info in the automation editor and then go to the device from the overflow your will still navigate away while losing your changes. I wonder if we can go 1 step deeper and intercept the navigate call...

[bramkragten]

There are a few cases that are not handled by this solution, as it only works for anchor links. Like if you open the more info in the automation editor and then go to the device from the overflow your will still navigate away while losing your changes. I wonder if we can go 1 step deeper and intercept the navigate call...

Actually looks like this is not really an issue atm, as an automation is not part of a device and the other related items and history and logbook do use anchors...

[silamon]

There are a few cases that are not handled by this solution, as it only works for anchor links. Like if you open the more info in the automation editor and then go to the device from the overflow your will still navigate away while losing your changes. I wonder if we can go 1 step deeper and intercept the navigate call...

2 options I could think of (not easy ones :D)

• Catch it in the custom router, although this is after navigate is already called, the url already been changed, so pushing back there is a little too late since you need to modify the history again at that point if you want to remain on the page.
• Implement something similar like how we handle dialogs, being done in the navigate call, so before history is modified.

Neither one of the solutions allows to access the component to ask if it's dirty, so it will need to be a static piece of memory somewhere.