diff options
| author | xhwang@chromium.org <xhwang@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-10-14 21:22:05 +0000 |
|---|---|---|
| committer | xhwang@chromium.org <xhwang@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-10-14 21:22:05 +0000 |
| commit | a941d4e57a9c663e2c9feb3779fef16f8f3f7457 (patch) | |
| tree | 943ddcf1cce5dfa16131ce1bead16b0955895c38 /ppapi/tests | |
| parent | b6b41cca31a6742abf132d4175befa81d359c639 (diff) | |
| download | chromium_src-a941d4e57a9c663e2c9feb3779fef16f8f3f7457.zip chromium_src-a941d4e57a9c663e2c9feb3779fef16f8f3f7457.tar.gz chromium_src-a941d4e57a9c663e2c9feb3779fef16f8f3f7457.tar.bz2 | |
Handle CdmWrapper::Initialize() failure gracefully.
Since CdmWrapper::Initialize() doesn't report error, GenerateKeyRequest() et al
can be called even if Initialize() failed previously.
For MediaKeys calls, we should fire KeyError when they are called without valid
|cdm_|. For Decryptor calls, we should fire the callback with error code.
Also added EncryptedMediaTest.ExternalClearKeyInitializeCDMFail test to cover
this case. Chrome will claim that the ClearKey CDM supports key system
"org.chromium.externalclearkey.fail". But actually ClearKey CDM will return NULL
for this key system in CreateCdmInstance();
BUG=306241,179570
TEST=Unit tests added.
Review URL: https://codereview.chromium.org/27030007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@228528 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ppapi/tests')
0 files changed, 0 insertions, 0 deletions