Automations save despite closing the save modal to cancel saving

[TimeBomb]

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

When creating a new automation (via duplicating an existing automation or creating a new empty one), when attempting to cancel saving that automation by clicking the "X" in the save modal, the automation is instead created.

Describe the behavior you expected

Upon clicking the "Save" button and then clicking the "X" in the save automation modal that appears, I expect the automation to not be saved and instead keep me on the unsaved automation creation form.

Steps to reproduce the issue

1. Go to existing automation
2. Duplicate it
3. Click Save button
4. Click top right "X" in the save modal that appears
5. Notice that automation is now saved and appears in the main automations list ...

What version of Home Assistant Core has the issue?

2022.9.0

What was the last working version of Home Assistant Core?

2022.8.7

In which browser are you experiencing the issue with?

Chrome 105.0.5195.102

Which operating system are you using to run this browser?

Windows 11

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.

[TimeBomb]

I can confirm this issue still occurs.

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

[karwosts]

Still an 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.