WordPress/wp-includes/js/mediaelement
2016-01-20 15:47:28 +00:00
..
background.png
bigplay.png
bigplay.svg Upgrade MediaElement to 2.18.1 - monkey-patches to allow H264 in Chromium. 2015-09-11 18:35:26 +00:00
controls.png
controls.svg
flashmediaelement.swf Upgrade MediaElement to 2.18.1 - monkey-patches to allow H264 in Chromium. 2015-09-11 18:35:26 +00:00
froogaloop.min.js After [31016], would be cool if we actually included the froogaloop file to interact with Vimeo. 2015-01-09 20:04:23 +00:00
jumpforward.png Upgrade MediaElement to 2.18.1 - monkey-patches to allow H264 in Chromium. 2015-09-11 18:35:26 +00:00
loading.gif
mediaelement-and-player.min.js MediaElement: apply monkey patch to include a PR which fixes a breaking change made upstream on a public interface: 2015-09-20 02:31:24 +00:00
mediaelementplayer.min.css Upgrade MediaElement to 2.18.1 - monkey-patches to allow H264 in Chromium. 2015-09-11 18:35:26 +00:00
silverlightmediaelement.xap Ugrade to MediaElement 2.16.4: 2015-03-05 16:54:26 +00:00
skipback.png Upgrade to MediaElement 2.16.2 2014-11-30 05:58:24 +00:00
wp-mediaelement.css RIP #21759b, the old WordPress Blue. 2015-10-21 18:36:28 +00:00
wp-mediaelement.js Media: When reusing the initial values from the global MediaElement config object, the config object should first be cloned. Objects in JS are references that will retain any changes. This fixes an issue where player controls could get mixed up between instances when multiple players (namely, single audio and audio playlists, in a certain order) are on the same page. 2016-01-20 15:47:28 +00:00
wp-playlist.js Media: When reusing the initial values from the global MediaElement config object, the config object should first be cloned. Objects in JS are references that will retain any changes. This fixes an issue where player controls could get mixed up between instances when multiple players (namely, single audio and audio playlists, in a certain order) are on the same page. 2016-01-20 15:47:28 +00:00