docs: add hover card / tooltip example to eventMouseEnter#249
Open
kenlyle2 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes fullcalendar/fullcalendar#5517
What this adds
A Hover Card / Tooltip (no external library) section to
eventMouseEnter.mdcovering:getBoundingClientRect()+position: fixeduseState+useReffor the same patternWhy no library
Third-party tooltip libraries (Tooltip.js, Tippy.js) expect to own the DOM lifecycle of their anchor element. FullCalendar re-renders event elements on navigation, which breaks most library attachment strategies. The
position: fixed+ state approach sidesteps this entirely and has zero additional dependencies.This pattern is running in production at PostGlider, a social-media scheduling app built on Next.js + FullCalendar v6, across both month and week views.
Related