-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should WebRTC be [SecureContext] #228
Comments
Per https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts/features_restricted_to_secure_contexts it seems browsers are moving in that direction. I'm not sure if [SecureContext] will work (e.g., perhaps there are sites assuming that interfaces exist), but restricting it to secure contexts in prose should be doable at least. |
@dontcallmedom your feedback is solicited on this topic. Yves will follow up with context. |
TAG doesn't really have objections to asking WebRTC to make it [SecureContext]. Implementations have already started moving the feature to [SecureContext]… See https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts/features_restricted_to_secure_contexts. (Note Safari does restrict |
From my testing, at least |
We should probably specify when we're talking about |
Thanks a lot for following up on this. We have checked all the PRs on the spec side and yes, we are very happy to see this change. Thank you for flying TAG! We are excited to see how the next generation comes out. |
As noted here, we are wondering whether we should ask WebRTC spec to be in [SecureContext]. Here's our issue to discuss...
CC @annevk, @alvestrand
The text was updated successfully, but these errors were encountered: