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

[Feature Policy] Should (sensorless) "inline" "viewer" sessions be allowed without the XR policy-controlled feature? #731

Closed
ddorwin opened this issue Jun 21, 2019 · 2 comments
Assignees
Labels
feature policy All things related to Feature Policy privacy-and-security Issues related to privacy and security
Milestone

Comments

@ddorwin
Copy link
Contributor

ddorwin commented Jun 21, 2019

[This is one of the decisions to make as part of resolving #308 and #729.]

There shouldn't be any privacy concerns for "inline" sessions using the "viewer" reference space. Should it be possible for applications to create such sessions and reference spaces without any WebXR-related policy-controlled feature enabled (i.e., without "xr" or "vr") or should it not be possible to successfully request any session without a/the "base" feature enabled?

@ddorwin
Copy link
Contributor Author

ddorwin commented Jul 19, 2019

The outcome of #308 is that all features included in "VR complete" are controlled by "xr". Thus, the answer to this question is "no."

/agenda to discuss this along with #730 - see that issue for more details.

@probot-label probot-label bot added the agenda Request discussion in the next telecon/FTF label Jul 19, 2019
@NellWaliczek NellWaliczek modified the milestones: July 2019, August 2019 Jul 19, 2019
@AdaRoseCannon AdaRoseCannon removed the agenda Request discussion in the next telecon/FTF label Jul 30, 2019
@toji
Copy link
Member

toji commented Aug 19, 2019

Nell and I talked this over again today, and the general response that we came to was that polyfilling is an appropriate way to address scenarios where a developer wants inline, sensorless XR access in an environment where everything else is blocked. It allows for a significantly cleaner feature policy as well.

@toji toji closed this as completed Aug 19, 2019
@toji toji added the feature policy All things related to Feature Policy label Sep 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature policy All things related to Feature Policy privacy-and-security Issues related to privacy and security
Projects
None yet
Development

No branches or pull requests

5 participants