-
Notifications
You must be signed in to change notification settings - Fork 24
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
Hbbtv "video/broadcast" not working in Chrome, Firefox works #41
Comments
Thanks for this report and I will investigate. Previously at the beginning of this extension, it was only working under Firefox (as main targeted platform) and not tested that much on Chrome/Opera/Edge now based on Chromium codebase. And I assume that under latest Win10, you are now testing with Edge. I will try. |
After testing this page, I can see inside the DevTools console that Chrome has a certificate issue with the site holding the mp4 example and moreover it needs a user click to unlock the video playback as indicated in the error message In the meantime, I found a quick solution by replacing line 562 (holding the video url http://clips.vorwaerts-gmbh.de/VfE_html5.mp4) inside
Then you will be able to see the new https video rendered and when clicking on it, it will play properly. I hope in the future that I will be able to replace the standard video tag with a WebAssembly video player which will not have those browser tricks to handle. |
Thanks, I did the same changes on a local files but Chrome(win10, latest chrome) does nothing. Firefox works fine with the same extension app folder. Error in chrome console so my version is semi broken at the moment, downloaded the fresh github+applied Bottom-right corner should have a broadcast video.
Changes in
|
Chrome is unable to mockup
video/broadcast
object but Firefox works. Latest browsers in Win10.Simple test app, bottom right corner should run video.mp4 placeholder.
https://refapp.hbbtv.org/dash/broadcast-object/broadcast-object.html
<object type="video/broadcast" id="broadcastVideo"> </object>
The text was updated successfully, but these errors were encountered: