Scott Taylor cee318ed81 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. ... Props Fab1en. Fixes #34152. Built from https://develop.svn.wordpress.org/trunk@36364 git-svn-id: http://core.svn.wordpress.org/trunk@36331 1a063a9b-81f0-0310-95a4-ce76da25c4cd		2016-01-20 15:47:28 +00:00
..
background.png
bigplay.png
bigplay.svg
controls.png
controls.svg
flashmediaelement.swf
froogaloop.min.js
jumpforward.png
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
silverlightmediaelement.xap
skipback.png
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