Skip to content
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

Section 3.2: Streaming should not require user prompts without sending media #119

Merged
merged 6 commits into from
Jul 27, 2023

Conversation

xingri
Copy link
Contributor

@xingri xingri commented Jul 13, 2023

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

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 xingri force-pushed the add-cloud-game-constraints branch from d98f186 to 6cd5522 Compare July 13, 2023 18:45
@aboba aboba changed the title Clarify Game streaming requirements (section 3.2) Section 3.2: Add Requirement N48 Jul 13, 2023
@aboba aboba changed the title Section 3.2: Add Requirement N48 Section 3.2: Game streaming can not require user prompts if media access is not needed Jul 13, 2023
@aboba
Copy link
Collaborator

aboba commented Jul 13, 2023

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 aboba changed the title Section 3.2: Game streaming can not require user prompts if media access is not needed Section 3.2: Game streaming should not require user prompts if it is not sending media Jul 13, 2023
@xingri
Copy link
Contributor Author

xingri commented Jul 13, 2023

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."

Thank you @aboba. That sounds more clearer.

@aboba
Copy link
Collaborator

aboba commented Jul 14, 2023

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>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 aboba changed the title Section 3.2: Game streaming should not require user prompts if it is not sending media Section 3.2: Streaming should not require user prompts if it is not sending media Jul 15, 2023
@aboba aboba changed the title Section 3.2: Streaming should not require user prompts if it is not sending media Section 3.2: Streaming should not require user prompts without sending media Jul 15, 2023
Copy link
Member

@jan-ivar jan-ivar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

index.html Outdated Show resolved Hide resolved
index.html Show resolved Hide resolved
Co-authored-by: Jan-Ivar Bruaroey <[email protected]>
@alvestrand
Copy link
Contributor

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>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
without prompts for camera and microphone permissions.</td>
without access to camera or microphone.</td>

@aboba aboba merged commit 8950db1 into w3c:main Jul 27, 2023
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants