| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Body grew on hover because the absolutely-positioned tooltip was appended to
document.body without top/left, so its static-flow position extended
body.scrollWidth/scrollHeight during layout measurement.
Switch both the use:tooltip directive and LinkedTooltip's measurement div to
position:fixed, which is relative to the viewport and does not contribute to
the body's scroll area. The directive now also uses clientX/clientY (dropping
the scrollY offset for the pin branch), removes the 100ms mousemove debounce,
and drops the top/left transition so the tooltip tracks the cursor without
feeling laggy or sliding in from the page top.
|
| |
|
|
| |
This reverts commit 6865cae76cb88aa78d7c297c637557468fdce8fc.
|
| |
|
|
|
|
| |
Absolute-positioned tooltips were appended to document.body without initial
left/top, so their static-flow position extended body scrollWidth/scrollHeight
during layout, briefly enlarging the page on hover.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
LinkedTooltip appends its tooltip div directly to document.body in
createTooltip and only removes it from hideTooltip. If the component
was destroyed while the tooltip was visible (e.g. parent navigated
mid-hover), the div leaked and stayed in the DOM forever.
Add an onDestroy handler that clears the pending hide/debounce timers
and, if the tooltip div is still parented to document.body, removes
it. Guarding on parentNode avoids double-removal when hideTooltip has
already run.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|