fix: use JavaScript-based hover for checkpoint menu visibility #10056
+62
−11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #8344
Fixes the checkpoint restore button not displaying on hover on Rocky Linux and some Windows configurations.
Problem
PR #7985 changed the checkpoint menu to be hidden by default and only visible on hover using Tailwind's
group-hover:blockCSS class. However, this CSS-based hover approach doesn't work reliably on all platforms, creating a chicken-and-egg problem where users can never see the checkpoint buttons to click them.Solution
Replaced CSS-based hover (
group-hover:block) with JavaScript-based hover usingonMouseEnter/onMouseLeavehandlers withuseState. This approach:MermaidButton.tsx,ImageViewer.tsx, andMarkdown.tsxChanges
isHoveringstate and mouse event handlers toCheckpointSaved.tsxmenuVisible = isHovering || isPopoverOpen || isClosinggroup-hover:blockclass dependencyTesting
Fixes #8344