Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

For dynamic contents, always set a very high duration #1220

Merged
merged 1 commit into from
Feb 20, 2023

Conversation

peaBerberian
Copy link
Collaborator

I found out that the video element's duration property for live contents was sometimes very close to the maximum position, whereas it should be set to very high number for such types of contents.

The reason behind this issue was very clear: the MediaDurationUpdater only performed a live-specific logic when the current tracks' duration are initially not known whereas it should do it everytime the duration may need to be updated.

I found out that the video element's `duration` property for live
contents was sometimes very close to the maximum position, whereas
it should be set to very high number for such types of contents.

The reason behind this issue was very clear: the `MediaDurationUpdater`
only performed a live-specific logic when the current tracks' duration
are initially not known whereas it should do it everytime the duration
may need to be updated.
@peaBerberian peaBerberian added bug This is an RxPlayer issue (unexpected result when comparing to the API) Priority: 0 (Very high) This issue or PR has a very high priority. Efforts should be concentrated on it first. labels Feb 20, 2023
@peaBerberian peaBerberian added this to the 3.30.0 milestone Feb 20, 2023
@peaBerberian peaBerberian merged commit 3b9af1b into next Feb 20, 2023
@peaBerberian peaBerberian deleted the misc/live-duration-updates branch July 6, 2023 12:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This is an RxPlayer issue (unexpected result when comparing to the API) Priority: 0 (Very high) This issue or PR has a very high priority. Efforts should be concentrated on it first.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant