HTML5 WebP capture + Google Font auto-registration on export#116
Open
dazzatronus wants to merge 3 commits into
Open
HTML5 WebP capture + Google Font auto-registration on export#116dazzatronus wants to merge 3 commits into
dazzatronus wants to merge 3 commits into
Conversation
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.
Summary
Html5Playerduration-detection logic — frame count now bakes the full clip uniformly.getEdit()/export auto-registers catalogued Google Fonts a clip references intotimeline.fonts, so an edit built without an explicitadd_fontstill renders with the correct font instead of falling back or failing.Test plan
tests/font-autoregister.test.ts)fonts[]entry → correct font in outputNote
SDK now requires canvas ≥ 2.8.2 (calls
computeHtml5FrameCountwithoutdetectedDurationMs). Dependency is currently^2.8.0— bump the floor to^2.8.2before merge.