@remotion/studio: Disable freeze frame outside visible range

[JonnyBurger]

Summary

• Disable the sequence freeze-frame action when the playhead is outside the sequence's visible range.
• Keep the action disabled during premounting and postmounting frames.
• Remove the freeze JSX prop when unfreezing instead of writing freeze={null}.
• Add regression coverage for the visible range boundaries.

Test plan

• bun run build
• bun run stylecheck
• cd packages/studio && bun run test
• cd packages/studio-server && bun test src/test/update-sequence-props.test.ts

Closes #9713

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
bugs	Ready	Preview, Comment	Jul 27, 2026 12:26pm
remotion	Ready	Preview, Comment	Jul 27, 2026 12:26pm

[pullfrog]

✅ No new issues found.

Reviewed changes — a clean guard that disables the freeze-frame menu item when the playhead is outside the sequence's visible [from, from+duration) range, plus a boundary unit test.

• Add isSequenceVisibleAtTimelinePosition — checks whether the timeline position falls within the sequence's output frame range, ignoring premounting/postmounting.
• Gate canToggleFreeze on visibility — adds the new check as the first guard in the canToggleFreeze chain so the menu item is disabled outside the visible range.
• Unit test boundary values — verifies position: 19/20/59/60 for a sequence at from: 20, duration: 40, confirming the half-open interval semantics.

  ^{｜ View workflow run ｜ Using DeepSeek Pro (free via Pullfrog for OSS) (Claude Opus not used — the program covers this model; add its provider key to run your pick) ｜ 𝕏}

[pullfrog]

✅ No new issues found.

Reviewed changes — the new commit replaces null with undefined when removing the freeze prop, so unfreeze now removes the attribute from JSX instead of writing freeze={null}. A updateSequenceProps test confirms the prop-stripping behavior.

• null → undefined on unfreeze — in use-sequence-freeze-frame-menu-item.ts, the remove path now passes undefined as the value, which causes updateSequenceProps to strip freeze= from the JSX output.
• Test for optional-attribute removal — new updateSequenceProps test that sets freeze to undefined and asserts the output no longer contains freeze=.

  ^{｜ View workflow run ｜ Using DeepSeek Pro (free via Pullfrog for OSS) (Claude Opus not used — the program covers this model; add its provider key to run your pick) ｜ 𝕏}