New issue
Advanced search Search tips

Issue 659374 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug

Blocked on:
issue 659828



Sign in to add a comment

MediaKeySession: Resolve the promise returned by close() after resolving the closed promise attribute

Project Member Reported by ddorwin@chromium.org, Oct 25 2016

Issue description

Per https://w3c.github.io/encrypted-media/#close, the Session Closed algorithm, which resolves the MediaKeySession's `closed` attribute is to be run synchronously before resolving the promise returned by the `close()` method. See https://github.com/w3c/web-platform-tests/issues/4058 for more details.

Currently, Chrome runs these steps in the opposite order, resulting in the promise resolve handlers running in the opposite order (and thus passing the incorrect test identified in the web-platform-tests issue above).
 
Status: Started (was: Available)
I'll fix Clear Key, but we need a CDM update to fix Widevine.
Owner: ddorwin@chromium.org
Cc: -rkuroiwa@chromium.org
Owner: rkuroiwa@chromium.org
Status: Assigned (was: Started)
Clear Key is fixed and passing the corrected spec test passes.

We need to fix Widevine so that https://www.w3c-test.org/encrypted-media/drm-mp4-playback-temporary-events.html will pass.
This should also be done for remove().
#5 is a separate bug.
Blockedon: 659828

Sign in to add a comment