frontend
frontend copied to clipboard
home-assistant
Menu items remain highlighted after mouse hover until page reload (2025.5.1)
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.
- [x] I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.
Describe the issue you are experiencing
In the 2025.5 version of Home Assistant, menu bar items (such as those on the left navigation panel) remain highlighted after hovering over them with the mouse, even if they are not selected. This makes multiple items appear "active" or "focused" at the same time. It gets fixed when the page is manually reloaded (F5). The issue also happens with the default theme, and no custom frontend modifications or HACS elements are required to reproduce it. ⚠️ This issue only occurs in Chromium-based browsers (Chrome, Edge, Brave). It does not happen in Firefox.
Describe the behavior you expected
Only the selected menu item should remain highlighted; previous hover effects should be cleared properly.
Steps to reproduce the issue
Steps to reproduce:
1)Open Home Assistant in a browser.
2)Navigate for automations, enter in one.
3)Hover over multiple items in the sidebar.
4)Notice that previously hovered items stay highlighted as if selected.
5)Press F5 or reload the page.
6)The highlight behavior now works correctly — only the current item is shown as selected.
⚠️ This issue only occurs in Chromium-based browsers (Chrome, Edge, Brave). It does not happen in Firefox.
What version of Home Assistant Core has the issue?
2025.5.1
What was the last working version of Home Assistant Core?
2025.4
In which browser are you experiencing the issue?
Google Chrome Versión 136.0.7103.93 (Build oficial) (64 bits)
Which operating system are you using to run this browser?
Windows 11 Pro 24H2
State of relevant entities
This issue occurs even with no custom cards or themes. It appears to be a frontend rendering/state issue introduced in the 2025.5 release.
Problem-relevant frontend configuration
Javascript errors shown in your browser console/inspector
Additional information
No response
Same problem here. Screenshot here: https://github.com/home-assistant/core/issues/144432#issuecomment-2861921315
I am also having the same issue. In my particular environment, I have even tested with and without all custom stuff (safe mode), which make no difference at all. I was able to reproduce it quite easily, while moving from one dashboard to another (pointing to a subview).
On Edge I could not reproduce it, but on Chrome, on 2 different laptops, even on new environments, incognito mode, clear all browser cache.
Even the Home Assistant demo site is having the issue. Open the full menu, hit the humidity badge, it will open a graph, close it and hover your mouse over the menu items.
Forgot to mention, running on Windows 11 24H2 26100.3476 and Chrome Version 136.0.7103.93 (Official Build) (64-bit)
I also have this problem and could track it down to this:
- Go to https://demo.home-assistant.io/#/lovelace/home
- Open the full "Spotlights" control
- All
md-rippleelements will be stuck after hovering them. - Looks like the
pointerleaveevent is no longer triggered.
https://github.com/user-attachments/assets/63e2442a-e5fc-4e7e-a250-97f36c21a874
After triggering the pop-up nothing is printed to the console anymore.
Same here. But only with Chrome/Edge browser. Firefox does not have this issue.
How to reproduce:
- Latest clean core from dev without any integration or resources installed
- Click on an entity on the dashboard to open a sub window and close it Menu items will now stay highlighted when hover until page is reloaded
Still happening on 2025.5.3.
Weird not many more people and the devs themselves seem to be affected. You would think this very obvious issue would have been picked up by now.
Still happening on 2025.5.3. As posted, started in 2025.5.1. On the default theme.
Same here, experiencing the same problem. Hope this gets fixed soon as it's quite annoying.
What OS/browser version is this happening on?
Can't reproduce on MacOS with latest Chrome
In my case it is happening on 2 laptops, both running on Windows 11 24H2 26100.3476 and Chrome Version 136.0.7103.93 (Official Build) (64-bit) @bramkragten
What OS/browser version is this happening on?
Can't reproduce on MacOS with latest Chrome
I'm on macOS 15.5 (24F74) with Chrome Version 137.0.7151.56 (Official Build) (arm64), and the issue is still happening for me.
What OS/browser version is this happening on?
Can't reproduce on MacOS with latest Chrome
Windows 11, on Edge Version 136.0.3240.92 (Official build) (64-bit) Windows 11, on Edge Version 137.0.3296.52 (Official build) (64-bit)
Windows 11 Chrome Version 137.0.7151.56 (Official Build) (64-bit)
Sent from Outlookhttp://aka.ms/weboutlook
From: hapklaar @.> Sent: Friday, May 30, 2025 9:18 AM To: home-assistant/frontend @.> Cc: festion @.>; Manual @.> Subject: Re: [home-assistant/frontend] Menu items remain highlighted after mouse hover until page reload (2025.5.1) (Issue #25428)
[https://avatars.githubusercontent.com/u/7703320?s=20&v=4]hapklaar left a comment (home-assistant/frontend#25428)https://github.com/home-assistant/frontend/issues/25428#issuecomment-2922526698
What OS/browser version is this happening on?
Can't reproduce on MacOS with latest Chrome
Windows 11, on Edge 136.0.3240.92 (Official build) (64-bit)
— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/frontend/issues/25428#issuecomment-2922526698, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHLCD4DRCYNCHH5XWJU3L433BBSB7AVCNFSM6AAAAAB43U4EDOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMRSGUZDMNRZHA. You are receiving this because you are subscribed to this thread.Message ID: @.***>
⚠️ This issue only occurs in Chromium-based browsers (Chrome, Edge, Brave). It does not happen in Firefox.
All Chromium browsers have the problem
⚠️ This issue only occurs in Chromium-based browsers (Chrome, Edge, Brave). It does not happen in Firefox.
All Chromium browsers have the problem
Apparently there is some nuance as @bramkragten says he doesn't have the issue on his mac with Chrome. Curious what the difference is.
Win 10 Just updated to Version 137.0.7151.56 (Official Build) (64-bit), and weirdly enough:
Win 10 Just updated to Version 137.0.7151.56 (Official Build) (64-bit), and weirdly enough:
Did you first click on an entity to open it? This is how I trigger the problem
I just updated to 137.0.7151.56 and the issue is still there, interestingly I have to identical machines with the same chrome version and one is experiencing this issue and one is not.
Trying to understand what is the difference between the machines I remembered I enabled experimental web platform features Chrome:
chrome://flags/#enable-experimental-web-platform-features
This is usually needed to flash firmware devices directly from Chrome, disabling this feature fixes the issue, I tried enabling and disabling it few times and when it is disabled the issue is gone.
Nice catch. I have this enabled in edge as well. When I disable it the issue is gone for me too.
edge://flags/#enable-experimental-web-platform-features
ps I have this enabled for a feature of the flasher for Mi thermometers
Trying to understand what is the difference between the machines I remembered I enabled experimental web platform features Chrome:
chrome://flags/#enable-experimental-web-platform-featuresThis is usually needed to flash firmware devices directly from Chrome, disabling this feature fixes the issue, I tried enabling and disabling it few times and when it is disabled the issue is gone.
I can confirm this, just disabled it and since then, it is working like a charm. For me, the reason to enable it, was also for flashing Xiaomi thermometers from Bluetooth to Zigbee.
I few months ago I had a similar issue and tracked it down to this chromium issue (I even added home assistant demo as a repro website): https://issues.chromium.org/issues/41487938
Disabling chrome's BoundaryEventDispatchTracksNodeRemoval flag mitigates the issue.
Disabling chrome's
BoundaryEventDispatchTracksNodeRemovalflag mitigates the issue.
How to disable this? ----edit---- found it chrome://flags/#boundary-event-dispatch-tracks-node-removal
Disabling chrome's
BoundaryEventDispatchTracksNodeRemovalflag mitigates the issue.How to disable this? ----edit---- found it chrome://flags/#boundary-event-dispatch-tracks-node-removal
that flag is not available in Edge from what I can see :(
Disabling chrome's
BoundaryEventDispatchTracksNodeRemovalflag mitigates the issue.How to disable this? ----edit---- found it chrome://flags/#boundary-event-dispatch-tracks-node-removal
that flag is not available in Edge from what I can see :(
In case you missed it, in Edge you can workaround this bug by disabling
edge://flags/#enable-experimental-web-platform-features
that flag is not available in Edge from what I can see :(
In case you missed it, in Edge you can workaround this bug by disabling
edge://flags/#enable-experimental-web-platform-features
Yeah, but I sadly need that enabled for work 🙈