WebXR permission levels can be accessed and "modified" via an enabled permissionLevelButton when that button should be disabled, e.g. when on a non-XR site.
This could lead to confusing UX that presents options that aren't relevant for the presented context.
The permissionLevelButton should be disabled and unresponsive to taps unless on a WebXR page & permissions have already been granted/denied for that page.
WebXR permission levels can be accessed and "modified" via an enabled permissionLevelButton when that button should be disabled, e.g. when on a non-XR site.
This could lead to confusing UX that presents options that aren't relevant for the presented context.
The permissionLevelButton should be disabled and unresponsive to taps unless on a WebXR page & permissions have already been granted/denied for that page.