feat(studio): model logical timeline navigation#2712
Draft
miguel-heygen wants to merge 1 commit into
Draft
Conversation
Collaborator
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Jul 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Add a pure logical navigation model for timeline tracks, clips, property lanes, keyframes, and ease segments.
Why
Keyboard movement must follow the editor's semantic structure rather than whichever DOM nodes happen to be mounted by virtualization.
How
Introduce deterministic navigation identities and directional traversal with focused coverage for boundary, collapsed, and expanded-lane cases. This PR depends only on Family F's live-clock extraction.
Test plan
Family F tip validation: 200 focused timeline/navigation tests, 3,012 full Studio tests, Studio typecheck, format, lint, file-size gate, and full workspace build.