Permissions-Policy: gamepad directive
Experimental:This is anexperimental technology
Check theBrowser compatibility table carefully before using this in production.
The HTTPPermissions-Policy headergamepad directive controls whether the current document is allowed to use theGamepad API.
Specifically, where a defined policy blocks use of this feature, calls toNavigator.getGamepads() will throw aSecurityErrorDOMException. In addition, thegamepadconnected andgamepaddisconnected events will not fire.
Syntax
Permissions-Policy: gamepad=<allowlist>;<allowlist>A list of origins for which permission is granted to use the feature. See
Permissions-Policy> Syntax for more details.
Default policy
The default allowlist forgamepad isself.
Examples
General example
SecureCorp Inc. wants to disable the Gamepad API within all browsing contexts except for its own origin and those whose origin ishttps://example.com.It can do so by delivering the following HTTP response header to define a Permissions Policy:
Permissions-Policy: gamepad=(self "https://example.com")With an <iframe> element
FastCorp Inc. wants to disablegamepad for all cross-origin child frames, except for a specific<iframe>.It can do so by delivering the following HTTP response header to define a Permissions Policy:
Permissions-Policy: gamepad=(self)Then include anallow attribute on the<iframe> element:
<iframe src="https://other.com/game" allow="gamepad"></iframe>iframe attributes can selectively enable features in certain frames, and not in others, even if those frames contain documents from the same origin.