-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
[Question] Best way to pass options to sourcehandler? #3129
Comments
Sounds similar to #2616. |
Hmmm interesting, didn't see #2616 yet. |
Sounds good. Should we close this then and make sure that #2616 is updated to address updating options after initialization as well? |
I think what I want would even work without updating options after initialization. Or at least, if you define "initialization" as "when calling Anyway, I think this can be closed. |
Yeah, I mean that we need a good way of giving options to source handlers on initialization but also afterwards. |
This is not really an issue, but more of a question.
Say I want to pass options to a sourcehandler. In particular, I want to be able to pass an option to
videojs-contrib-dash
whether it should use the portal to limit bitrate (i.e. callsetLimitBitrateByPortal
on the Dash.js MediaPlayer).What is the best way to do this?
I know I could pass it as an option during player initialization in the
html5
tech, but then the way to get to it would be to calltech.options()
in the source handler and apparently that function is going away.Normally you'd set the options you need during the construction of a component, but that is not really possible with a source handler I think. So what is a good way?
The text was updated successfully, but these errors were encountered: