Switch level on "internal-error" key status #7414
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR will...
Switch level on "internal-error" key status.
Why is this Pull Request needed?
Requested by @yajin2021 in #7401 and #7413.
Are there any points in the code the reviewer needs to double check?
Should recovery be attempted if an "internal-error" key status is received, or will all keys (including current "usable" keys) error in tow?
According to the spec, no. We probably should not do this:
https://www.w3.org/TR/encrypted-media-2/#dom-mediakeysessionclosedreason-internal-error
Resolves issues:
#7413
Checklist