[Bug]: Directive::XR_SPATIAL_TRACKING injects vr header value instead of xr-spatial-tracking

[cemrich]

Contact Details

[email protected]

What happened?

I am running v2.1 and using the Directive::XR_SPATIAL_TRACKING directive, in a custom FeaturePolicy like so:

<?php

namespace App\Http\FeaturePolicies;

use Mazedlx\FeaturePolicy\Directive;
use Mazedlx\FeaturePolicy\Policies\Policy;

class CustomFeaturePolicy extends Policy
{
    public function configure(): void
    {
        $this->addDirective(Directive::XR_SPATIAL_TRACKING, [
            'self',
            'https://sketchfab.com/',
        ]);
    }
}

This does inject the Permissions-Policy header just fine, uses the correct origin values, but uses the outdated vr key instead of xr-spatial-tracking:

Chrome 122 is not happy with this key:

Given the fact, that there is a Directive::VR property for people to use, I would consider this behaviour a bug.

Thank you very much for this great package and please let me know, if you need more context!

(PS: The code of conduct leads to example.com)

Version

2.0.0

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[mazedlx]

@cemrich thank you for bringing this to our attention, the bug is fixed in the latest release.

[cemrich]

Thanks a whole lot for your work!

[mazedlx]

We're happy to help!