Tooltip Flickering & EDGE_CONFIG Handling

[cyberkunju]

1. Tooltip Flickering Issue

The Problem:
The tooltips on the main page, such as those on the colored dots in the top-left corner of the main window, would disappear the moment a user's mouse cursor left the trigger element. This made it impossible to move the mouse onto the tooltip to read its content, creating a poor user experience.

The Fix:
The issue was resolved by implementing a more robust hover-state management system for the Tooltip component.

• A short delay was added before the tooltip hides when the mouse leaves the trigger element.
• The tooltip itself was made "aware" of the mouse. If the cursor moves from the trigger element directly onto the tooltip, the timer to hide it is canceled, and the tooltip remains visible.
• This allows users to seamlessly interact with the tooltip content without it vanishing unexpectedly.

---

2. EDGE_CONFIG Handling Error

Issue #27

The Problem:
The application would crash on startup if the EDGE_CONFIG environment variable was not set in the environment. This variable is intended to be optional for loading special configurations (like those for enterprise users), but the code was written in a way that required it to be present, preventing developers or users on standard plans from running the application easily.

The Fix:
The fix was made in the server-side code that handles session creation. The part of the code that attempts to read the Vercel Edge Config is now wrapped in a try...catch block.

• If the EDGE_CONFIG variable is present and valid, the application uses it.
• If it is missing or invalid, the code now catches the resulting error, logs a message indicating that it's falling back to defaults, and allows the application to continue running smoothly with its standard configuration.
• This makes the feature truly optional as intended.

[vercel]

@cyberkunju is attempting to deploy a commit to the browserbase Team on Vercel.

A member of the Team first needs to authorize it.