-
Notifications
You must be signed in to change notification settings - Fork 1.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
element.getAttribute is not a function error in v2 beta3 #473
Comments
Can you please provide a manifest URL with which I could reproduce this error? |
@mlondon1, we cannot reproduce. Can you provide a manifest URL that reproduces the error? |
Hi, This is encrypted premium content, is there anything else that I can provide? Or do you not need to play the content and just want to look at the MPD? |
We need some way to reproduce your issue before we can solve it. Can you provide instructions on how to reproduce the issue? Usually, a good repro involves a manifest URL and license server URL that can be used in the demo app. If you can't provide those things publicly, you can always send me a private email with the details. My email address can be found in CONTRIBUTORS. |
Thanks for the manifest info. I've tracked the bug down to here: shaka.media.TtmlTextParser.getInheritedAttribute_ = function(
element, attributeName) {
var ret = null;
while (element) {
ret = element.getAttribute(attributeName); Now that we have repro, it should be easy to fix. Thanks! |
You're welcome |
@mlondon1, please try again with the latest from |
Hi,
I am seeing the following error in Shaka player v2.0.0-beta3 that I do not see in beta2 when attempting to play my Widevine-Dash VOD content in Google Chrome
streaming_engine.js:1148 (text:3) failed fetch and append: code=undefined(anonymous function) @ streaming_engine.js:1148
player.js:1614 Assertion failed: Wrong error type!shaka.Player.onError_ @ player.js:1614(anonymous function) @ streaming_engine.js:1149
main.js:182 Player error TypeError: element.getAttribute is not a function(…)
The text was updated successfully, but these errors were encountered: