perf(studio): define timeline viewport budgets and fixtures#2696
Draft
miguel-heygen wants to merge 1 commit into
Draft
Conversation
Collaborator
Author
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
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
Define measurable timeline viewport budgets, diagnostics, and deterministic large-project fixtures before changing rendering behavior.
Why
Timeline performance needs an explicit, reproducible contract. Without fixed DOM, latency, memory, and fixture budgets, later virtualization work could appear faster while silently dropping content or moving work elsewhere.
How
This is D1 of the independent Family D draft Graphite stack. Its review base is the immutable, PR-less Family C baseline; Families A-C do not need to merge for this PR to be reviewed. It supersedes the owned behavior from legacy PRs #2631 and #2632, which remain open for audit until landing.
Test plan
Validated on the exact Family D tip with 279 focused tests, the full Studio suite (2,939 passed; 18 todos), Studio Server files tests (67 passed), both package typechecks, oxfmt, oxlint, diff and file-size checks, Fallow with zero introduced findings, and two consecutive strict 50,000-element Chromium passes.