keystatuschange event with status = 'released' fails. |
||||||||||
Issue descriptionAfter calling MediaKeySession.remove(), the CDM is expected to send a keystatuschange event with all keys tagged as 'released'. However, when that happens: [1:1:1118/160357:FATAL:ppapi_messages.h(98)] Check failed: (static_cast<int>(value) >= static_cast<int>(0) && static_cast<int>(value) <= static_cast<int>(PP_CDMKEYSTATUS_STATUSPENDING)). Range checked for PP_CdmKeyStatus is incorrect (not allowing PP_CDMKEYSTATUS_RELEASED).
,
Nov 22 2016
,
Nov 30 2016
As this affects the W3C EME tests, requesting permission to merge this into M56.
,
Nov 30 2016
Your change meets the bar and is auto-approved for M56 (branch: 2924)
,
Nov 30 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/a40ddfb7300ac34f01e3d0bf41ae7d6dea222b99 commit a40ddfb7300ac34f01e3d0bf41ae7d6dea222b99 Author: John Rummell <jrummell@chromium.org> Date: Wed Nov 30 23:13:43 2016 Merge "Fix range checking for PP_CdmKeyStatus" The specified maximum value doesn't allow PP_CDMKEYSTATUS_RELEASED, so update it. BUG= 666975 TEST=Tested with W3C EME tests Review-Url: https://codereview.chromium.org/2514123004 Cr-Commit-Position: refs/heads/master@{#433754} (cherry picked from commit c24785e7ff8bf6ce47d903b598d813e1bbd17fab) Review URL: https://codereview.chromium.org/2541193002 . Cr-Commit-Position: refs/branch-heads/2924@{#224} Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059} [modify] https://crrev.com/a40ddfb7300ac34f01e3d0bf41ae7d6dea222b99/ppapi/api/private/pp_content_decryptor.idl [modify] https://crrev.com/a40ddfb7300ac34f01e3d0bf41ae7d6dea222b99/ppapi/c/private/pp_content_decryptor.h [modify] https://crrev.com/a40ddfb7300ac34f01e3d0bf41ae7d6dea222b99/ppapi/proxy/ppapi_messages.h
,
Mar 4 2017
,
Apr 17 2017
,
May 30 2017
,
Aug 1 2017
,
Oct 14 2017
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by bugdroid1@chromium.org
, Nov 22 2016