Section 3.2: Streaming should not require user prompts without sending media #119
Conversation
Add the constraints to Cloud Gaming application that allow users to use the application without accessing any user media resources. Partial fix for w3c#103
xingri
force-pushed
the
add-cloud-game-constraints
branch
from
d98f186
to
6cd5522
Compare
aboba
changed the title
aboba
changed the title
|
I would change the text to: "An application that is only receiving but not sending media can operate without prompts for camera and microphone permissions." |
aboba
changed the title
Thank you @aboba. That sounds more clearer. |
|
Updated the language and renumbered the requirement to N36. |
index.html
Outdated
| <tr> | ||
| <td>N36</td> | ||
| <td>An application that is only receiving but not sending media can operate | ||
| without prompts for camera and microphone permissions.</td> |
There was a problem hiding this comment.
Agreed. If you don't want camera access you shouldn't have to ask for it as a workaround to APIs lacking in other areas.
aboba
changed the title
aboba
changed the title
There was a problem hiding this comment.
I gather this is referring to ICE gathering?
RFC 8828 Section-5.2 says "Mode 1 MUST NOT be used unless user consent has been provided. The details of this consent are left to the implementation; one potential mechanism is to tie this consent to getUserMedia (device permissions) consent, described in [RFC8827], Section 6.2. Alternatively, implementations can provide a specific mechanism to obtain user consent."
As stated, user agents are already allowed to "provide a specific mechanism to obtain user consent", but it's also true this hasn't happened yet.
Specs can't mandate UX, but it looks like good work was already happening here with a "direct-connection" permission descriptor in w3c/permissions#196 (comment).
@lgrahl @alvestrand Looks like that PR got dropped over a technicality? I.e. this would go into a "Permissions Integration" section of webrtc-pc rather than into the permissions spec itself. Was there a reason this was dropped, or should we resume work here?
Co-authored-by: Jan-Ivar Bruaroey <[email protected]>
|
The bug about adding a permission specifically for network access is w3c/webrtc-extensions#87 I think the language needs a small tweak - it's not that those apps are unable to operate at all today when not asking for microphone/camera access, it is that they in some cases operate less efficiently. The case of not operating at all (when you're in an environment where mDNS doesn't work, and external connectivity is not available, for instance) is a corner case. |
index.html
Outdated
| <tr id="N36"> | ||
| <td>N36</td> | ||
| <td>An application that is only receiving but not sending media can operate | ||
| without prompts for camera and microphone permissions.</td> |
There was a problem hiding this comment.
| without prompts for camera and microphone permissions.</td> | |
| without access to camera or microphone.</td> |
Add the constraints to Cloud Gaming application that allow users to use the application without accessing any user media resources.
Partial fixes for #103
Preview | Diff