[Bug]: website docs navbar hover/dropdown disappears when you try to click on a dropdown menu item

[JSONbored]

Summary

When hovering on the main navbar docs link, a dropdown appears with other docs links. However, if you try to click on those links, the dropdown menu itself disappears, so you can never actually click any of the links in the dropdown menu.

Area

Frontend UI

Expected behavior

Should remain open when you try to click the links.

Actual behavior

Dropdown menu disappears/closes when you hover away from the Docs navbar link, meaning docs links can never actually be clicked.

Reproduction

No response

Validation

No response

Public-safety check

• I removed secrets, tokens, wallet details, private keys, local paths, and private scoring output.

[dosubot]

The root cause is the mt-3 (12px margin gap) between the trigger element and the dropdown panel in apps/gittensory-ui/src/components/site/site-header.tsx [1]. The wrapper <div> uses onMouseEnter/onMouseLeave to toggle docsOpen state [2], but because the dropdown is positioned with top-full mt-3, there's a 12px dead zone between the trigger and the dropdown. When the cursor crosses that gap, onMouseLeave fires and closes the dropdown before you can reach it.

A few fix options:

1. Bridge the gap with padding instead of margin — replace mt-3 with pt-3 on the dropdown wrapper so the hover area remains contiguous.
2. Add an invisible bridge element — insert a transparent element (e.g. ::before pseudo-element or a zero-opacity div) that spans the gap and keeps the cursor "inside" the container.
3. Debounce the close — add a small timeout (~150–200ms) on onMouseLeave and clear it on onMouseEnter, so rapid cursor traversal through the gap doesn't trigger a close:

const closeTimeout = useRef<NodeJS.Timeout | null>(null);

const handleMouseEnter = () => {
  if (closeTimeout.current) clearTimeout(closeTimeout.current);
  setDocsOpen(true);
};

const handleMouseLeave = () => {
  closeTimeout.current = setTimeout(() => setDocsOpen(false), 150);
};

Option 1 (padding swap) is the simplest one-line fix if you're fine with the visual spacing staying the same.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.