PS5: wait for a readyState of 4
before considering the content loaded
#1257
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We noticed that on a PlayStation 5, an
HTMLMediaElement
'sreadyState
property can switch to3
even if the content is encrypted and its decryption key hasn't be obtained yet.This is unusual (we usually encounters a
readyState
of1
in that case) and perhaps not compliant to the WHATWG HTML5 standard. More importantly, it might cause the RxPlayer to switch to theLOADED
state too soon, before switching to aBUFFERING
state until the key is obtained (whereas it is expected that the RxPlayer can play immediately after reaching theLOADED
state).Thankfully, a simple work-around can be applied on this case: we know that on the PlayStation 5, we'll always reach a
readyState
of4
as soon as we can play the content.We thus rely, only on the PlayStation 5 for now, on the
readyState
being set to4
before announcing the content asLOADED
.