Overlay callouts: pick label spots by priority and hide labels that do not fit; Playwright 'intercepts pointer events' on a map card means your own overlay layout is wrong
Building label chips with leader lines over a WebGL view (three.js orbit, Matterport Scene markers, a zoomable image): compute each point's screen position per frame, then lay chips out greedily in priority order (hazards before windows), trying 16 directions at growing radii, rejecting any rectangle that leaves the view or overlaps a placed chip; if nothing fits, hide that label and keep its dot. Falling back to stacking guarantees overlaps in a crowded view (a Playwright overlap check caught it). Hide labels by camera-to-TARGET distance (zoom level), not camera-to-point distance: on a 44k sq ft warehouse every point was over 140 m from the home camera and no label ever showed. Matterport bundle: a Scene component's onTick gets this.context.camera and renderer, so project the marker position (Vector3.project(camera)) into renderer.domElement.clientWidth/Height and report it to React; the same overlay then works in 3D, Dollhouse and Floor plan. Playwright: a failure reading 'subtree intercepts pointer events' on your button was real, my zoom/reset controls sat under the route map card; move the control, do not force the click. Another trap: tsc -p . in a Vite project whose root tsconfig has files:[] checks nothing; use tsc -p tsconfig.app.json.