#Youtube iframe api update#
#Youtube iframe api code#

ytplayer.getCurrentTime())ĭo you guys know that the old YT.htm script fails the same test too? It works ok in SuperMemo though. Additionally, attempting to operate the player via the custom panel will throw a number of object doesn't support property or method errors wherever player API functions are used (e.g. The video will load but the onReady() event will not be fired. Save it to a local hard drive, and open it from a disk in Internet Explorer. The upgraded player with the minimum necessary implementation: Nevertheless, a question asking to elaborate on the number of security restrictions was posted at Stack Overflow Test case

Since then it has become the new recommended API superseding both Flash API (A3) and JavaScript API. If you expand the very first message in the linked thread, you will discover it was related to the IFrame Player API, which, at that time, was at the experimental stage. If so, how were the restrictions in the old JavaScript/Flash version resolved in SuperMemo? Perhaps we should keep posting and asking there for clear answers/solutions? If Jeff Posnick is from YouTube API Team, he might be the best person to ask (on behalf of all users of SuperMemo)! If this is a discussion from 2012, it might be relevant to the old API. There are a number of security restrictions that prevent http: and file: resources from talking to each other, both in the postMessage() JavaScript calls and in the Flash runtime Question

should we all not bombard Google or Microsoft with complaints about this 'progress'? if this is about their wars, why do users of SuperMemo suffer?.

could this be some outcome of Google-Microsoft wars? If so, who is the likely culprit?.

why do local files with the new HTML YouTube API cause problems in Internet Explorer, while Chrome or Firefox have no issues?.

why does the YouTube player version=2 still work despite the changes in the API.

#Youtube iframe api update#

why did the switch in the API coincide exactly with the update to Internet Explorer (including changes to security settings such as copying from the clipboard)(by 'exactly', I mean: 'down to a single showdown-restart cycle').the event which fires whenever a player has finished loading and is ready to begin receiving API calls, if it is run locally.Ĭould this be caused by a setting in Internet Explorer itself? You say the problem with incremental video comes from a change in YouTube API.

In Internet Explorer, the YouTube IFrame Player API does not issue the onReady() event, i.e.

What are the YouTube API changes that threaten incremental video in all versions of SuperMemo?.

Supporting the current YouTube IFrame Player API for YouTube-based incremental video requires changes to SuperMemo that are not backward-compatible. Those hiccups have only be fully resolved in version 17.3.Īs of Jul 1, 2018, SuperMemo 15 Freeware, version 15.5, uses the new YouTube API There are few minor issues with handling keyboard shortcuts though. If you want to use new YouTube API in older SuperMemos, you will need to substitute your yt.htm script with the new version (see: Workaround). You can run this script from your own server. The dependence on the server can be changed with one parameter in the script. The change of execution mode was caused by a bug in YouTube API for which we received no feedback from Google support in 12 months. Privacy: We do not collect user data while running the script. The new script is a stub that runs the actual script from server. SuperMemo 17.3 uses a script named YouTube.htm in place of the old yt.htm which you can now delete (folder in).

The posts will be retained for archiving purposes, and for users of older versions of SuperMemo. This means that all posts related to problems with upgrading to new YouTube API are no longer relevant. 7.2 Mitigating the external server dependencyĪs of Dec 1, 2017, SuperMemo 17 for Windows, version 17.3, uses the new YouTube API in incremental video script.

#Youtube iframe api code#

Īnd a set of javascript added in custom code to do certain things on those items $(''). The implementation process is based on data-custom attributes added to HTML nodes, like div etc. All controls are written here: YouTube Player API Reference for iframe Embeds | YouTube IFrame Player API | Google Developers. What that website you provided as an example has, is a set of custom JavaScript functions to communicate with Youtube Player API. Hey think the problem is not about people not willing to respond in the thread, but the fact that it’s a complicated process – especially that it’s written here: YouTube Player API Reference for iframe Embeds | YouTube IFrame Player API | Google Developers.