fix(import): preserve native video assets and range controls - #584
Draft
marcodantonio-netsons wants to merge 1 commit into
Draft
marcodantonio-netsons wants to merge 1 commit into
marcodantonio-netsons wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
Static-site import kept native video URLs outside the asset rewrite pipeline and dropped poster/preload metadata. Range inputs became text fields and lost their step; the canvas also omitted numeric bounds. Use one asset-property list for normalization and rewriting, preserve video affordances, and support range/step through the canonical TypeBox input schema, editor and publisher.
Verified with 506 targeted import/form tests, build, lint and diff checks, plus a 15-test collaboration/canvas rerun including native range bounds. Full suite: 7,056 passed and one timeout in the existing read-only collaboration reset test; the targeted rerun passed, but the full-suite timing failure remains under investigation. Browser verification on the migrated homepage confirms video playback from uploaded media, eco pause/resume, and native range controls. No database schema changes.