-
Notifications
You must be signed in to change notification settings - Fork 28
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 getDisplayMedia be functional in SecureContext only? #77
Comments
Are these two alternatives? |
These are alternatives. |
I also prefer the second. |
What are the behavioral differences from this choice?
Where "some error" is what, Neither Feature Policy nor the Permissions spec seem to mention specific errors. |
It's 1. "An interface, namespace, or member construct is exposed" in an insecure context if it's available in both secure and non secure contexts, which boils down to [SecureContext] in WebIDL. |
Makes sense to me. This is a new powerful method. |
Ping if there was any consensus/decision on this. |
Yes, see w3c/mediacapture-main#540 (comment). |
Fixed by #86. |
Following on w3c/webrtc-pc#1945, the question is whether to mandate secure origins for getDisplayMedia.
We could:
The text was updated successfully, but these errors were encountered: