The valid configuration warning is persistent

[WRoss7]

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 pressing the "check configurations" button, the validation warning "Configuration valid!" appears and remains persistent until I refresh the page from the browser. But if I do not refresh it, and resume editing the Configuration.yaml file, when I then return to the validation page, I still find the "Configuration valid!" warning. This can be confusing to a novice user

Describe the behavior you expected

Imo, the "Configuration valid!" warning should disappear after a few seconds (e.g., after 3 sec. with fading effect), and also it should be more prominent

Steps to reproduce the issue

...

What version of Home Assistant Core has the issue?

Home Assistant 2022.9.4

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Chrome 105.0.5195.127

Which operating system are you using to run this browser?

Windows 10

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.

[WRoss7]

Again

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

[WRoss7]

Persistent 😄

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

[WRoss7]

Up

[karwosts]

Fix pr filed.

[WRoss7]

Thank you...little things that can confuse new users