-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
Tight coupling with controlBar component #7689
Comments
👋 Thanks for opening your first issue here! 👋 If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can. |
Having a control bar is definitely the default use-case. We probably don't test enough with trying to disable default components.
if our build doesn't like Are you interesting in submitting a PR? |
You'll need to create your own fork of the repo, make your changes in a branch, then a pull request to propose the changes from your branch are added to Video.js. There's a quick walkthrough here: https://opensource.com/article/19/7/create-pull-request-github |
Added condition to resetProgressBar_ method
Done |
Fixes #7689 Co-authored-by: alex <try2betheb3st@gmail.com> Co-authored-by: Pat O'Neill <pgoneill@gmail.com>
Fixes videojs#7689 Co-authored-by: alex <try2betheb3st@gmail.com> Co-authored-by: Pat O'Neill <pgoneill@gmail.com>
Description
We have tight coupling in player.js Class Player method resetControlBarUI_(), when using reset() method.
ControlBar component may be not exists or exists on another nesting level..
Steps to reproduce
Use player.reset() method, when in player object there is no controlBar child/component at property "children"
Results
Expected
Reset player instance
Actual
We have error
Error output
Additional Information
versions
videojs
7.17.1
browsers
all
OSes
all
(Sorry for my bad english)
The text was updated successfully, but these errors were encountered: