New issue
Advanced search Search tips

Issue 616644 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
foolip@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug

Blocked on:
issue 658422


Sign in to add a comment

EME: Update HTMLMediaElement's readyState based on key availability

Project Member Reported by ddorwin@chromium.org, Jun 2 2016 
https://github.com/w3c/encrypted-media/issues/129 changes EME such that key availability affects the associated HTMLMediaElement's readyState value. This also implies all events that are implied by transitions in readyState.

Specifically:
1. When the element is "waitingforkey", readyState is set to HAVE_METADATA. [1]
2. Upon resuming playback (e.g. due to a key becoming available), readyState is set to HAVE_CURRENT_DATA or higher, as appropriate. [2]

[1] https://w3c.github.io/encrypted-media/#queue-waitingforkey
[2] https://w3c.github.io/encrypted-media/#resume-playback

Comment 1 by foolip@chromium.org, Jun 2 2016 

Will it be possible to implement this using only WebMediaPlayerClient::readyStateChanged()? If it looks just like any other resource from the perspective of HTMLMediaElement, it's easier to be confident that all the right code paths are being triggered.

Comment 3 by ddorwin@chromium.org, Nov 8 2016

Blockedon: 658422
The waitingforkey part, at least, is implemented but there is a bug: issue 658422.
Project Member

Comment 4 by sheriffbot@chromium.org, Nov 8 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by yini...@chromium.org, Nov 14 2017

Status: Available (was: Untriaged)
this bug is blocked on 658422 whose status is available. so change this bug status to available too.
Project Member

Comment 6 by sheriffbot@chromium.org, Nov 15

Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by dougman@chromium.org, Dec 21

Status: WontFix (was: Untriaged)
Closing as Won't Fix.  The blocking bug has been resolved as Won't Fix.

Comment 8 by ddorwin@chromium.org, Dec 21

Status: Available (was: WontFix)
The blocked-on bug is Assigned.
►

Sign in to add a comment