Skip to content

Say why an export opened from inside its ZIP has no background - #398

Merged
singhharsh1708 merged 1 commit into
mainfrom
fix/missing-frames-notice
Sep 18, 2026
Merged

singhharsh1708 merged 1 commit into
mainfrom
fix/missing-frames-notice

Conversation

@singhharsh1708

Copy link
Copy Markdown
Owner

Reported with a screenshot: an export of an uploaded clip showed its section headings on a black page. The address bar read AppData\Local\Temp<id>_, which is where Windows puts a file you double-click while still inside a ZIP. It copies that one file and leaves the frames folder behind.

Reproduced in Chrome with the same export in two folders:

background failed requests
index.html with frames/ beside it paints (mean colour 10/79/101) 2, lenis and the favicon, absent from the test folder
index.html alone, as opened from inside the ZIP pure black (0/0/0) 14, including all 12 frames

The page gave no hint why. When every keyframe of the set being drawn fails to load, the export now shows a notice explaining that the frames folder is not beside the page and that the ZIP needs extracting first, and it stops requesting the rest of the set. A healthy export never shows it. After this change the same two folders give: extracted, background painted and no notice; alone, the notice in view, marked role=alert, and 5 failed requests instead of 14.

The README said the opposite of what happens: that an extracted export opened by double-click would not show its background, because browsers block file:// pages from reading neighbouring files. The frames load as images, which Chrome allows, and the extracted folder above paints. It now tells the owner to extract the whole ZIP first and why.

Tests run the emitted loader against images that all fail and all load, and check the notice appears only in the first case. Both fail against main. Also ran: tsc, eslint, 537 vitest tests, production build.

On Windows, double-clicking index.html inside the ZIP copies that one file
to a temporary folder and leaves the frames behind, so the page loads with a
black background and nothing to explain it. When every keyframe fails to load,
the exported page now shows what happened and what to do. The README said the
opposite of what happens: an extracted export opened by double-click paints
its frames in Chrome, since they load as images. It now says to extract first.
@vercel

vercel Bot commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

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

Project Deployment Actions Updated
scrollcraft Ready Ready Preview Sep 18, 2026 8:06am UTC

@singhharsh1708
singhharsh1708 merged commit 6d14bc6 into main Sep 18, 2026
3 checks passed
@singhharsh1708
singhharsh1708 deleted the fix/missing-frames-notice branch September 18, 2026 08:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant