Repository navigation
feat: export html5 clips in the browser - #283
Merged
Merged
Conversation
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 31, 2026
# [2.31.0](v2.30.1...v2.31.0) (2026-10-31) ### Features * export html5 clips in the browser ([#283](#283)) ([8ab73fc](8ab73fc))
|
🎉 This PR is included in version 2.31.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
The export check sends every html5 clip to a cloud render. It was added in #225, when export read an html5 frame before it had finished drawing. #229 made export wait for each frame, and #277 to #281 fixed what drew differently in Safari and Firefox. The rule now only costs people a cloud render for edits the browser exports faithfully.
On a 15 s html5 edit with audio and a large embedded photo, compared with a cloud render (SSIM):
Export now draws each clip with
prepareStaticRender({ strict: true }). An html5 frame that can't be drawn, or a clip whose page didn't load, fails the export instead of leaving the clip out, so the host can fall back to a cloud render. Snapshots still leave just that clip blank.htmlassets other than the plain-text form still go to the cloud.Verify:
npm run verify:ci. Then export an edit with an html5 clip in Chrome: it downloads an MP4 instead of reporting anhtmlissue.Risk: a host that counted on html5 always failing the check now gets a browser export for those edits.