Coming from here
BACKGROUND
The ActiveHoverable component manages hover states for interactive elements in our web interface. The current implementation is using multiple event listeners, including a global document-level mouseover listener, which is causing performance overhead, especially in views with many hoverable elements. For example, when hovering over chat messages, the CPU utilization can reach 100%.
PROBLEM
- Global mouseover event listener on document level is causing continuous event processing and being triggered on extremely frequently (on every mouse pixel move)
- Each hoverable instance adds its own document listener, multiplying the overhead
- High CPU usage during mouse movement across the page
- Redundant hover state checks and updates
SOLUTION
Optimize hover state management and CPU performance by:
- Removing the global document-level mouseover listener
- Using component-level mouse events only
- Implementing efficient state tracking with lastKnownHoverState
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021882410245975337736
- Upwork Job ID: 1882410245975337736
- Last Price Increase: 2025-01-23
- Automatic offers:
- brunovjk | Reviewer | 105822890
Issue Owner
Current Issue Owner: @johncschuster
Coming from here
BACKGROUND
The ActiveHoverable component manages hover states for interactive elements in our web interface. The current implementation is using multiple event listeners, including a global document-level mouseover listener, which is causing performance overhead, especially in views with many hoverable elements. For example, when hovering over chat messages, the CPU utilization can reach 100%.
PROBLEM
SOLUTION
Optimize hover state management and CPU performance by:
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @johncschuster