Fix #220: Remove deprecated support for insecure contexts #271
Conversation
This file contains 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
|
On what timeline will Chrome start enforcing secure origin? When the info is available, I'd like to announce to the shaka-player-users list the date or Chrome release where this will happen. |
|
@joeyparrish: Support on insecure contexts has been deprecated in Chrome for over a year, and we have seen content providers switching to HTTPS. While we have not yet given a timeline for enforcement, I expect that to happen soon, and we will clearly communicate this in Chrome and via other channels. We believe this spec change is an important step in presenting a consistent message - and eventually behavior - to authors as well as implementers. |
|
Changes look good. |
|
Looks good to me. |
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.
Also updated text related to use of the APIs on insecure contexts.
The algorithm step is replaced with the
[SecureContext]IDL attribute as discussed in #269.