Quick answer: After positioning the tooltip, measure its rect and flip its pivot or clamp its position so it stays fully inside the canvas regardless of cursor location.
Hovering an item near the screen edge shows a tooltip that spills off the side and gets cut. A fixed offset that ignores bounds is the cause. Here is how to fix it.
How to fix it
1. Measure the tooltip rect
After the layout updates, read the tooltip's width and height (force a Canvas.ForceUpdateCanvases() if needed) so you know its real size before placing it.
2. Flip near edges
If the tooltip would exceed the right or bottom edge, anchor it to the left of or above the cursor instead, flipping the pivot rather than overlapping the pointer.
3. Clamp inside the canvas
As a final step, clamp the tooltip's position so its rect stays within the canvas bounds, guaranteeing it is fully visible even in corners.
Catching the ones you can't reproduce
The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.
Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.
This is where a tool like Bugnet earns its place. Its SDK captures every Unity error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.
The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.