Load clusters right after the header is parsed.
Previously we can only start loading clusters after the key is added (KeyAdded received) to avoid decryption error. This is solved after http://crrev.com/149952 is landed.
BUG=none
TEST=This demo works on latest chrome build with r149952.
Change-Id: Idaa7a1a321d08fee8097dd070088801376bc5c1d
diff --git a/AUTHORS b/AUTHORS
index 2b40abd..2cdcc19 100644
--- a/AUTHORS
+++ b/AUTHORS
@@ -1,4 +1,4 @@
-
Aaron Colwell <[email protected]>
Frank Galligan <[email protected]>
+Xiaohan Wang <[email protected]>
Google Inc.
diff --git a/adaptive/dash_player.js b/adaptive/dash_player.js
index 4fe5a26..a2e81f4 100644
--- a/adaptive/dash_player.js
+++ b/adaptive/dash_player.js
@@ -612,7 +612,7 @@
* @return {string} version.
*/
DashPlayer.version = function() {
- return '0.2.1.0';
+ return '0.2.2.0';
};
/**
@@ -995,9 +995,6 @@
*/
DashPlayer.prototype.doKeyAdded = function() {
this.log('doKeyAdded() : ');
- // TODO(xhwang): Remove and restore original call point when Chrome is capable
- // of resuming playback when key is added. See http://crbug.com/125753.
- this.loadFirstClusters();
};
/**
@@ -1335,11 +1332,8 @@
this.changeState(DashPlayer.LOADING);
this.appendData(infoTracks);
- // TODO(xhwang): Until Chrome is capable of resuming playback when a key is
- // added, we must not load the clusters. See http://crbug.com/125753.
- // For now, only do this if EME is not enabled.
- if (!this.videoElement.webkitAddKey)
- this.loadFirstClusters();
+
+ this.loadFirstClusters();
};
/**
