Update eme_player to handle MediaKeySession.generateRequest()

Update eme_player to handle MediaKeySession.generateRequest()

Modify the createSession() call to use the new version (0 parameters)
and call generateRequest() once it is available.

BUG=358271
TEST=EME browser_tests pass with and without generateRequest() changes

Committed: https://crrev.com/e42508865f7eeef0528c562d0dffc1fc9088cf22
Cr-Commit-Position: refs/heads/master@{#293975}

[jrummell, 2014-09-05 18:24:03]

jrummell@chromium.org changed reviewers:
+ ddorwin@chromium.org, xhwang@chromium.org

[jrummell, 2014-09-05 18:24:04]

PTAL. This updates the browser_tests so they will continue to work once
MediaKeySession.generateRequest() is implemented.

[ddorwin, 2014-09-08 17:50:09]

https://codereview.chromium.org/544283002/diff/1/media/test/data/eme_player_j...
File media/test/data/eme_player_js/player_utils.js (right):

https://codereview.chromium.org/544283002/diff/1/media/test/data/eme_player_j...
media/test/data/eme_player_js/player_utils.js:66: .catch (function(error) {
remove the space here and below

https://codereview.chromium.org/544283002/diff/1/media/test/data/eme_player_j...
media/test/data/eme_player_js/player_utils.js:67: Utils.failTest(error,
KEY_ERROR);
What is KEY_ERROR? Why do these all fail with that? Is this because the browser
tests don't differentiate more than this?

https://codereview.chromium.org/544283002/diff/1/media/test/data/eme_player_j...
media/test/data/eme_player_js/player_utils.js:72: if (PROMISES_SUPPORTED) {
Can we remove this now? Probably in a separate CL before this one.

[jrummell, 2014-09-08 18:21:06]

Updated.

https://codereview.chromium.org/544283002/diff/1/media/test/data/eme_player_j...
File media/test/data/eme_player_js/player_utils.js (right):

https://codereview.chromium.org/544283002/diff/1/media/test/data/eme_player_j...
media/test/data/eme_player_js/player_utils.js:66: .catch (function(error) {
On 2014/09/08 17:50:09, ddorwin wrote:
> remove the space here and below

Done. Note that clang-format wants to put the space back in.

https://codereview.chromium.org/544283002/diff/1/media/test/data/eme_player_j...
media/test/data/eme_player_js/player_utils.js:67: Utils.failTest(error,
KEY_ERROR);
On 2014/09/08 17:50:09, ddorwin wrote:
> What is KEY_ERROR? Why do these all fail with that? Is this because the
browser
> tests don't differentiate more than this?

KEY_ERROR is simply the string "KEY_ERROR". It is used since the tests simply
check the title when the test is finished to see if it succeeded or not.
(https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/med...)

https://codereview.chromium.org/544283002/diff/1/media/test/data/eme_player_j...
media/test/data/eme_player_js/player_utils.js:72: if (PROMISES_SUPPORTED) {
On 2014/09/08 17:50:09, ddorwin wrote:
> Can we remove this now? Probably in a separate CL before this one.

Yes. However, this test is done in several files, so I figured there would be
one cleanup pass after all the changes have been made.

[jrummell, 2014-09-09 01:01:03]

rebased now the PROMISES_SUPPORTED code is removed.

[ddorwin, 2014-09-09 17:23:30]

Thanks. LGTM

[jrummell, 2014-09-09 17:23:46]

The CQ bit was checked by jrummell@chromium.org

[commit-bot: I haz the power, 2014-09-09 17:25:16]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jrummell@chromium.org/544283002/40001

[commit-bot: I haz the power, 2014-09-09 18:51:58]

Committed patchset #3 (id:40001) as bf2b3678a6aa5269826e8cd779584392865e4016

[commit-bot: I haz the power, 2014-09-10 03:54:32]

Patchset 3 (id:??) landed as
https://crrev.com/e42508865f7eeef0528c562d0dffc1fc9088cf22
Cr-Commit-Position: refs/heads/master@{#293975}