W3C home > Mailing lists > Public > public-html-media@w3.org > October 2016

[encrypted-media] Should there be flexibility in when readyState is updated when waiting for a key?

From: ddorwin via GitHub <sysbot+gh@w3.org>
Date: Mon, 17 Oct 2016 22:00:19 +0000
To: public-html-media@w3.org
Message-ID: <issues.opened-183539732-1476741617-sysbot+gh@w3.org>
ddorwin has just created a new issue for 
https://github.com/w3c/encrypted-media:

== Should there be flexibility in when readyState is updated when 
waiting for a key? ==
Similar to #336, browsers may update `readyState` at different times. 
For example, Chrome currently waits three seconds before pausing 
playback due to video underflow to avoid glitching when the decoder 
falls slightly behind. The easiest and most consistent thing for 
Chrome to do would be to use the same behavior for missing key(s).

However, the Wait for Key algorithm currently requires that the 
`readyState` be updated before the `waitingforkey` event is fired 
(because it is fired by a task).

Do we want to be this prescriptive or should we provide more 
implementation flexibility? The suggestion in 
https://github.com/w3c/encrypted-media/issues/336#issuecomment-254346323
 might also provide such flexibility for this case.

@foolip @cpearce

Please view or discuss this issue at 
https://github.com/w3c/encrypted-media/issues/339 using your GitHub 
account
Received on Monday, 17 October 2016 22:00:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:49:17 UTC