Skip to content

Commit 99d9d95

Browse files
vanceingallsclaude
andcommitted
docs(studio): the saved-seek comment states what an overwrite does, not its history
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
1 parent 273f8bb commit 99d9d95

1 file changed

Lines changed: 2 additions & 3 deletions

File tree

‎packages/studio/src/player/hooks/useTimelinePlayer.ts‎

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -74,9 +74,8 @@ function usePreviewRefresh(deps: PreviewRefreshDeps) {
7474
// the iframe from the FIRST reload is mid-teardown: getAdapter() can still
7575
// return that dying document's adapter, whose getTime() reads 0 — and the
7676
// store's currentTime can lag the visual playhead. Overwriting the
77-
// still-unconsumed pendingSeek with either value is exactly how the
78-
// playhead used to end up at 0 after a Finder drop (verified live via a
79-
// currentTime write-trace). So: while a refresh is already in flight and a
77+
// still-unconsumed pendingSeek with either value puts the playhead at 0
78+
// after a Finder drop. So: while a refresh is already in flight and a
8079
// save exists, keep it; otherwise trust the live adapter, then the store.
8180
const refreshInFlight = isRefreshingRef.current && pendingSeekRef.current != null;
8281
if (!refreshInFlight) {

0 commit comments

Comments
 (0)