Bug title:Menu Bar Hover Effect Not Working Properly

[KinshukSS2]

Search before asking

• [x] I had searched in the issues and found no similar issues.

Operating System

• [ ] macOS
• [ ] Windows
• [x] Linux

Operating System Version

Ubuntu 25.04

It happens on the web browser too?

No, it just happens on the Desktop app

Rocket.Chat Desktop App Version

4.9.1

Rocket.Chat Server Version

7.13

Describe the bug

The hover effect on the menu bar (settings menu dropdown in the sidebar) doesn't work consistently. It requires an initial click to activate hover behaviour, and the hover state is lost when clicking elsewhere on the page.This creates an inconsistent and confusing user experience

https://github.com/user-attachments/assets/dee45e3e-aaf1-4dae-bd24-3851225c5abd

How to Reproduce

1. Launch the Rocket.Chat Desktop App

Build and start: yarn build && yarn start

2. Observe the menu bar (likely the sidebar with server/options menus)

Try hovering over menu items with dropdowns

3.Expected vs Actual Behavior: Bug: Hover does NOT trigger dropdowns on first interaction You must click on a menu item first

4.After clicking once:

Hover starts working - dropdowns appear on mouse hover This continues working temporarily

5. Click somewhere else on the page (outside the menu) Bug returns: Hover stops working again Must click a menu item again to re-enable hover

Describe your Expected behavior

The dropdown menu should consistently appear when hovering over the menu icon, without requiring an initial click to "activate" the hover state. The hover behavior should remain functional regardless of clicks elsewhere on the page.

Anything else

How often does this problem occur? Every time

-I also discussed this in the community and was advised to open an issue. It was mentioned that the behavior might be intentional, but I wanted to clarify this and ensure that it’s working as intended.

[vipulgupta28]

I think this is an OS native menu built via Menu.buildFromTemplate(). So the hover styling might be handled by the operating system and not by CSS. It’s often due to Electron bugs.