[LucaB01]

Problem

Ticket #227901 (Hubflo): a hotspot tooltip (the "?" next to a heading) floats over the page when the panel it sits in is scrolled, instead of staying next to its element.

Since 19.3.7 (#196) the hotspot anchor is position: absolute so it does not shift the element's layout. An absolutely positioned box is placed in the nearest positioned ancestor. When the element lives in a scrolling panel (overflow: auto) and that ancestor lies outside the panel, the hotspot keeps its viewport position while the content scrolls away, and only snaps back on a resize or re-render.

Fix

linkTooltip walks up from the element (or, next to a void element like input/img, its parent). The first scroll container (overflow: auto | scroll | overlay) found before any positioned ancestor gets position: relative, so the anchor's containing block scrolls with the content. Nothing changes when a positioned ancestor already sits inside the panel, or when there is no panel (the window scrolls the anchor anyway). The element itself is never touched, so overflow: hidden targets (truncated headings) are not clipped and the element's own absolutely positioned children keep their containing block.

The previous inline value is restored on unlink and on destroy() (which runs on every session change), but only while the inline value is still ours; repositionHotspot puts it back when a re-render reset the inline style.

Release

Bumps to 19.3.9 (package.json, lock, CHANGELOG, npm run build output in build/ and published/19.3.9 + published/latest), like the earlier chore: version commits.

Verified

• Repro page with a nested scrolling panel: with the published 19.3.8 bundle the heading moved 200px on scroll while the hotspot stayed at the same viewport top; with this build both move together, also for a truncated (overflow: hidden) heading whose hotspot stays visible next to the ellipsis. The panel gets position: relative, the headings keep no inline style.
• src/GleapTooltipManager.test.js (new): scroll container positioned, element left alone, positioned ancestor inside the panel, no panel, void element, restore on unlink / page-set value kept / destroy, re-apply on reposition. npm test: 599 passed.
• A second agent reviewed the first version; its two layout findings (clipping on overflow: hidden, re-anchored children) led to this scroll-container approach.

🤖 Generated with Claude Code