[user-github-me]

What

Keep metadata for saved Lottie animations larger than the 2 MB thumbnail limit in extracted/lottie-manifest.json.

Why

A valid Lottie file can embed a raster image and exceed the thumbnail limit while staying inside capture's 10 MiB validation limit. Capture saves the animation, but the preview size guard skips the entire file, so its dimensions, duration and file path disappear from the manifest.

Related work

#3811 established the existing capture validation and preview policy. #5293 fixes content deduplication in the save step; this correction concerns metadata after saving and can land independently. No matching open issue or competing implementation was found.

How

Apply the size guard only around thumbnail generation, then append the normal metadata entry with no preview property. The size limit, capture budgets and preview request policy keep their existing behavior.

Test plan

• The regression captures a valid 800 × 800 embedded PNG animation, checks that it exceeds the preview limit, and verifies its complete metadata, unchanged saved bytes, empty preview directory and absence of browser-page launches. It fails on main with the 16 existing media tests passing.
• All 47 tests pass across media capture, Lottie validation, Lottie discovery and preview request policy.
• Actual Chrome reproduction: a 2,566,131-byte Lottie animation is accepted, saved and rendered with 800 × 800 SVG image bounds. Main writes no manifest; fixed source writes the expected 3-second, 30-fps, one-layer entry while opening zero preview pages and preserving the animation bytes.
• Full workspace build, CLI build and typecheck, root lint, test reachability, formatting and normal pre-commit hooks pass.
• Comment citation and comment-share checks pass.

GitHub CI is passing, including Windows render. The later successful run supersedes the earlier dependency-installation timeout.

[jrusso1020]

Main still has if (fileSize > 2_000_000) continue; in renderLottiePreviews, which skips the manifest push along with the thumbnail, so saved Lottie files between 2 MB and the 10 MiB save limit vanish from lottie-manifest.json. The change scopes the size guard to the preview block only, the manifest entry is pushed without preview as the type already allows, and the budget breaks behave as before. The regression builds a real >2 MB embedded-image animation, asserts no page is opened, and checks the full manifest entry. The diff is mostly re-indentation; the logic change is the guard inversion.

Need: yes · Size: ok · Reuse: nothing to reuse · Simpler: already minimal

— Rames