Problem\nLabel-tie mode can produce labels that appear visually detached from nearby pins/routes, reducing trust in connectivity.\n\nAcceptance\n- Label anchors must remain within bounded distance of route/tie anchor\n- Hide/relocate labels that cannot satisfy non-overlap constraints\n- Add deterministic label-anchor metrics to compile status\n- Add fixture-based regression assertions
Problem\nLabel-tie mode can produce labels that appear visually detached from nearby pins/routes, reducing trust in connectivity.\n\nAcceptance\n- Label anchors must remain within bounded distance of route/tie anchor\n- Hide/relocate labels that cannot satisfy non-overlap constraints\n- Add deterministic label-anchor metrics to compile status\n- Add fixture-based regression assertions
Rbanh
added this to the Phase 10 - Readability & Routing Stabilization milestone 2026-02-20 02:07:34 -05:00
Related UX mitigation in 9a21e11: annotation/legend overlays are hidden in canvas by default to reduce detached/floating text noise while we complete label-anchor constraints.
Related UX mitigation in `9a21e11`: annotation/legend overlays are hidden in canvas by default to reduce detached/floating text noise while we complete label-anchor constraints.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem\nLabel-tie mode can produce labels that appear visually detached from nearby pins/routes, reducing trust in connectivity.\n\nAcceptance\n- Label anchors must remain within bounded distance of route/tie anchor\n- Hide/relocate labels that cannot satisfy non-overlap constraints\n- Add deterministic label-anchor metrics to compile status\n- Add fixture-based regression assertions
Related UX mitigation in
9a21e11: annotation/legend overlays are hidden in canvas by default to reduce detached/floating text noise while we complete label-anchor constraints.Shipped in
c247a33: selected component note hint now refreshes on selection render path (not only after movement/transform updates).