Feature-Policy: gamepad
Feature-Policy: gamepad
The HTTP Feature-Policy
header gamepad
directive controls whether the current document is allowed to use the Gamepad API. When this policy is disabled, calls to Navigator.getGamepads()
will throw a SecurityError
DOMException
. In addition, the gamepadconnected
and gamepaddisconnected
events will not fire.
Syntax
-
<allowlist>
-
A list of origins for which the feature is allowed. See Feature-Policy
.
Default policy
Default allow list for gamepad
is 'self'
.
General example
SecureCorp Inc. wants to disable the Gamepad API within all browsing contexts except for its own origin and those whose origin is https://example.com
. It can do so by delivering the following HTTP response header to define a feature policy:
With an <iframe> element
FastCorp Inc. wants to disable gamepad
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 feature policy:
Then include an allow 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.
Specifications
Browser compatibility
|
Desktop |
Mobile |
|
Chrome |
Edge |
Firefox |
Internet Explorer |
Opera |
Safari |
WebView Android |
Chrome Android |
Firefox for Android |
Opera Android |
Safari on IOS |
Samsung Internet |
gamepad |
86
|
86
|
91
["Only supported through the allow attribute on <iframe> elements.", "The default allowlist is * instead of self (as required by the specification)."]
|
No
|
72
|
No
|
No
|
86
|
91
["Only supported through the allow attribute on <iframe> elements.", "The default allowlist is * instead of self (as required by the specification)."]
|
No
|
No
|
No
|