vr in middlewares permissionsPolicy causing instability in Safari

[markchaik]

I noticed that I was not able to reach some of my services, using macOS Safari 15, via their FQDN - error 421. No issues in Chrome.

In the console, I noticed the following error in Chrome:

Error with Permissions-Policy header: Unrecognized feature: 'vr'.

In my middlewares.yml, I had:
permissionsPolicy: "camera=(), microphone=(), geolocation=(), payment=(), usb=(), vr=()
and so I removed the vr portion, resulting in
permissionsPolicy: "camera=(), microphone=(), geolocation=(), payment=(), usb=()" # removed VR due to errors

Now, no more issues with getting to my services Safari. I'm guessing this is a pretty new and less-supported feature, which is obviously messing with some browsers.

[xerifeazeitona]

I believe the vr policy has been deprecated over xr-spatial-tracking for some time now.

To disallow requests to use the virtual reality API you can use:
PermissionsPolicy: "camera=(), geolocation=(), microphone=(), payment=(), usb=(), xr-spatial-tracking=()"

source