Repository navigation
Keep valid HLS startup after floating-point playlist refreshes - #46
Merged
Merged
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.
An Hls.js playlist refresh can change a fragment start from
10.64to10.640000000000004. Exact comparison then cancels a valid pending startup as changed media. Accept only machine-precision round-off in start/duration, capped at one nanosecond; keep immutable media identity, actual geometry changes, authority, resource and deadline checks intact.The regression fails on the preceding public source and passes with the fix, preserving the exact original response/statistics/context and single terminal callback. It also checks real start/duration changes and the absolute cap on a large timeline. Update the API, status, changelog and generated AI context. Sustained playback and physical-device acceptance remain separate.
Validation: 128/128 warm-ahead tests, 19 targeted startup/framing checks, 202-module syntax, documentation and diff checks passed before push.