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

Is Trusted Immersive UI a conformance requirement? #719

Closed
NellWaliczek opened this issue Jun 19, 2019 · 7 comments · Fixed by #875
Closed

Is Trusted Immersive UI a conformance requirement? #719

NellWaliczek opened this issue Jun 19, 2019 · 7 comments · Fixed by #875
Assignees
Labels
fixed by pending PR A PR that is in review will resolve this issue. privacy-and-security Issues related to privacy and security trusted UI All things related to displaying trusted UI from the UA in VR/AR
Milestone

Comments

@NellWaliczek
Copy link
Member

[Disclaimer: This issue is one of several being filed to capture discussions that began either on #638, on #689, or at the most recent F2F]

This issue is NOT to discuss the requirements for what Trusted Immersive UI should look or behave like. That conversation is happening in #718

Instead, this issue tracks the question of whether a Trusted Immersive UI is a requirement for a UA to be considered conformant with WebXR.

(Note: this is also related to issue #702 which discusses figuring out what to do with non-XR feature permissions which developers may request during an immersive session)

@NellWaliczek NellWaliczek added the privacy-and-security Issues related to privacy and security label Jun 19, 2019
@NellWaliczek NellWaliczek added this to the July 2019 milestone Jun 19, 2019
@joshmarinacci
Copy link

The answer can only be yes: a trusted UI is a requirement. If a UA is not able to provide a trusted UI while in immersive mode then it must either ask for consent at the time the page requests immersive mode, or it should exit immersive mode when asking for consent. Essentially using non-immersive mode as the trusted UI.

@NellWaliczek
Copy link
Member Author

That's a pretty strong stance, Josh.

I think there's agreement that user consent should not be requested mid-session if trusted UI doesn't exist. But I don't think there's yet agreement that a User Agent is required to provide Trusted Immersive UI. If it didn't, the UA might alternatively choose to simply automatically reject the mid-session request. Which really, wouldn't be any different from a developer perspective since the feature being protected may not be available on all hardware anyway.

@ddorwin
Copy link
Contributor

ddorwin commented Jun 21, 2019

If it didn't [provide Trusted Immersive UI], the UA might alternatively choose to simply automatically reject the mid-session request. Which really, wouldn't be any different from a developer perspective since the feature being protected may not be available on all hardware anyway.

While the application would technically behave as if the user had denied consent, the developer probably doesn't expect that all users on a given user agent will be unable to use that part of their application. See the first paragraph of #720 (comment) for more discussion.

@NellWaliczek
Copy link
Member Author

Can you elaborate a bit, @ddorwin? I'm not quite following what you mean or how that's related to the comment in #720?

@avadacatavra
Copy link

I think that we can say something along the lines of:

For any mid-session prompts, UAs should either

  • use a trusted immersive UI to present the prompt to the user, where the trusted UI fulfills the requirements in What is Trusted Immersive UI? #718 OR
  • pause/suspend immersive mode in order to handle the prompt, then when it's resolved, reenter immersive mode

This will allow UAs to implement (or not) trusted UIs as they prefer

@Manishearth Manishearth added the help wanted This is a good issue for anyone to pick up and work on filing a PR for. label Sep 30, 2019
@Manishearth
Copy link
Contributor

Based on discussions at TPAC (mostly captured in @avadacatavra's comment), we should spec that "trusted UI" is a requirement (but not necessarily "trusted immersive UI") where trusted UI is either trusted immersive UI or "pause immersive mode and handle a prompt"

@Manishearth Manishearth self-assigned this Sep 30, 2019
@cwilso cwilso removed the help wanted This is a good issue for anyone to pick up and work on filing a PR for. label Oct 9, 2019
@cwilso cwilso modified the milestones: October 2019, November 2019 Oct 9, 2019
@NellWaliczek NellWaliczek removed their assignment Oct 10, 2019
@Manishearth Manishearth added the fixed by pending PR A PR that is in review will resolve this issue. label Oct 22, 2019
@Manishearth
Copy link
Contributor

will be fixed by #875

avadacatavra pushed a commit to avadacatavra/webxr that referenced this issue Nov 14, 2019
toji pushed a commit that referenced this issue Nov 15, 2019
kearwood pushed a commit to kearwood/webxr that referenced this issue Mar 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed by pending PR A PR that is in review will resolve this issue. privacy-and-security Issues related to privacy and security trusted UI All things related to displaying trusted UI from the UA in VR/AR
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants