Support #EXT-X-BYTERANGE before #EXT-X-MAP tag #5850
Merged
Conversation
This file contains 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
robwalch
force-pushed
the
feature/byterange-before-map-tag
branch
from
e78e89f
to
360652b
Compare
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.
This PR will...
byteRange,byteRangeEndOffset,byteRangeStartOffsettyping to reflect actual return types.fragment.byteRangereturns a number tuple or an empty arraybyteRangeEndOffsetandbyteRangeStartOffsetboth return numbers or both return undefinedWhy is this Pull Request needed?
Handle odd tag order in media playlists and better reflect data types.
Are there any points in the code the reviewer needs to double check?
Resolves issues:
Checklist