Skip to content

LOD overview exit can interrupt an animated zoom before its target #205

Closed

Description

@mvalancy

A real animated zoom from overview to items can stop before its requested scale. CSS stack run 40591493014 failed the existing 1440px LOD case: zoom target 1.2 remained at 1.1735656098434863 for the strict 5-second assertion. Phone passed; overall run failed. The trace points to zoomToTitle(1.2) at semantic-lod.spec.ts:222 after the test clock had resumed.

The overview-exit effect currently refits source titles by reissuing the current camera transform. D3 selection zoom.transform interrupts an active transition. When the 120ms minimap transition crosses the overview exit threshold (1.15), the effect can cancel its remaining movement.

Acceptance: refit newly visible source title geometry without issuing a camera command; add controlled-frame regression across the threshold; preserve exact requested transform, readable text, zero position writes, graph switching, keyboard/touch navigation and both viewport gates. No looser zoom tolerance or timeout increase.

I am implementing in isolated fix/lod-transition-ownership-20261027, from reviewed fixture-maintenance head 7fe08c5, ahead of the CSS/auth stack. Final root-cause review and negative-control reproduction are in progress.

Activity

  1. mvalancy commented on Oct 28, 2026

    @mvalancy
    MemberAuthor

    The camera-ownership correction (#207) updates visible title geometry without reissuing a zoom transform. Controlled-frame regression preserves the exact requested camera and confirms actual title measurement with zero layout writes at both widths. The original interrupted-transition failure and the withdrawn wrong-selector draft evidence remain documented.

    Verified integrated dev head: 780a7599d1d7949d5e0fac56091f0b07bb0e6e0d, complete tree cffa8b8a7903b9609603f1c42978511d900678f6, identical to independently reviewed and tested source 525ca4e5aa5bd4a918ad85165d0f2a0e8caf59ac.

    Final integrated CI and Comprehensive Tests passed every applicable job. Downloaded strict reports contain smoke 6, new-user 42, LOD 2, routes 7, mobile 27 and performance 3 passing cases, with zero failures, warnings, skipped cases, evidence errors, timeouts or nonzero exits. Both supported Node versions, real Neo4j, all three runtime images, effects and showcase passed. The main/nightly-only production job was inapplicable to this dev run; it is not credited as a pass. Earlier failures and cancelled intermediate runs remain retained.

    Integration used the owner's standing dev-only native admin authorization after independent exact-head review; that is not a non-author GitHub approval. Main remains 775362eace0723c57b7ba3c7936645c9d0d36cb4. No release, deployment or protection change occurred. Closing this bounded implementation issue after final branch acceptance, not claiming hosted or deployed-site clearance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions