Hello there. I am the developer of TwitchTheater.tv. I would like to use the new twitch player on my website, but it fails to load. I have been using iframes to embed it but all I get is a black screen. I didnt know where else to report this, so I posted it here. Hopefully this can get fixed so that I can release some new features for my website.
As far as I know Twitch is not officially supporting embedding of the new player just yet. I assume when itâs linked below on-site players through the âShareâ button it will be bug free and work properly. They still link the iframe for the old player for now.
Hello. Thank you for your answer. I am planning to add an option to my website that allows people to try out the new player so they can see the progress it makes as it develops, and then when its fully stable, I will officially make the move from flash to HTML5. But for the mean time, it would be really cool to see this get fixed. : )
Yes, Iâm frustrated as well. With the new player rolling out I would expect embedded players to work as expected. Currently it appears theyâre using the relative domain for the javascript code needed to populate the embeded html5 player with the required channel information.
If you check the source code on twitch.tv theyâre actually using iframes as well and the new player works just fine.
Embedding is broken again BibleThump
This time chrome console says âUncaught TypeError: Cannot read property âsplitâ of undefinedâ - player.dc9201cd.js.
I know you said chrome console but, which browser are you using just to make sure because Iâve had this issue too and brought it up on reddit with one of the devâs and it appears to work fine on chrome but on firefox it has this issue.
I understand your release cycle. However, the issue came back after your last release.
Now it has been two weeks with no change. Please keep us developers updated as to whatâs going on.
To quote my last reply below
Embedding the new HTML5 player still doesnât work in Chrome of Firefox. Both are giving âe is undefinedâ errors.
However, itâs working in Internet Explorer.
The reason for this is that IE throws an exception when a script tries to access cross-domain data in an iFrame. Chrome and Firefox only return an empty object without throwing an exception. Your code in player.js checks for an exception that is never thrown.