In w3c/webappsec-permissions-policy#49, "vr" was added to control "access to VR displays." This string, rather than "webvr" was intentionally chosen to be extensible to other APIs. #86 tracks adding relevant text to this spec.

Now that the spec has been renamed and is intended to cover more user cases, we should decide whether to also change the feature name, and, if so, to what.

On one hand, it makes sense to more closely match the spec and apply to all devices accessed by this spec/navigator.xr.requestDevice(). On the other hand, there may someday be legitimate reasons to provide access to VR but not AR (or vice versa), and, as with the original name, the scope need not be limited to the specific API. Perhaps the strongest argument for a single name is the position some have stated that AR and VR are points on an XR/MR continuum. In other words, there may be scenarios and devices in between for which the correct value may not be obvious.

We should make a decision soon then file a new issue in Feature Policy similar to the one above and update #86 with the correct string.

/cc @raymeskhoury @clelland