-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Shaka Player UI customization #6887
Comments
The "ui" variable of the video element or video container element should contain the UI object, once the UI has been set up. That has not been changed since the tutorial was written. It's hard to say what the exact problem might be without seeing your code, really. Are you putting the code snippet that configures the UI inside the init function, or just in the global context, perhaps? |
Thanks for your response! I agree that more detail should have been provided. I'm running the project under NextJS and am using React refs in order to retrieve the video element. I tried to retrieve it after initializing shaka, but I am still getting
The player works and plays videos, I'm only struggling with the UI (just to specify). Also again, I am unable to get the |
Oh, I see. The Shaka Player UI (e.g. If you are interested in creating your player through code, and not letting the Shaka UI setup scan the DOM and make the player for you, you should look at the section on "Programmatic UI setup" in the tutorial. |
What version of Shaka Player are you using?
-> 4.9.5
What browser and OS are you using?
-> Edge on Windows 10
Hi,
I have been trying to customize the UI of my shaka player, and following the documentation is just not working. It tells me to query the element and
["ui"]
, but to no success. I've also seen people doingshaka.ui.Overlay
and such things, but this "ui" object is not defined in my shaka object. So now I'm a bit confused as to if the documentation is outdated, and what I'm actually supposed to do to get around customizing the UI.Thank you!
The text was updated successfully, but these errors were encountered: