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

fix: use startTime instead of 0 for finiteDuration #1448

Merged
merged 1 commit into from
Nov 21, 2023
Merged

Conversation

adrums86
Copy link
Contributor

Description

We shouldn't set endTime to 0, instead we should set it to the startTime if we don't have a duration.

Specific Changes proposed

replace 0 with startTime

Requirements Checklist

  • Feature implemented / Bug fixed
  • If necessary, more likely in a feature request than a bug fix
  • Reviewed by Two Core Contributors

@adrums86
Copy link
Contributor Author

@dzianis-dashkevich a fix from a while ago that you brought to my attention re #1411.

@adrums86 adrums86 merged commit dc78d78 into main Nov 21, 2023
9 of 13 checks passed
@adrums86 adrums86 deleted the fix-finiteDuration branch November 21, 2023 17:40
@robert-schurig-mi
Copy link

With "@videojs/http-streaming": "3.0.2" the cues worked as expected and they get active because the endTime was set to Infinity.

Then the endTime of a cue was set to "0" and the stoped working, they don't get active and not event dispatch.

Now in the latest version "@videojs/http-streaming": "3.8.0" the endTime is set to the startTime... okay. sounds for me like an improvement... but the cue doesn't get active too.
So what does it fix ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants