Experimental: This is an experimental technology
Check the Browser compatibility table carefully before using this in production.
The HTTP Permissions-Policy header gamepad directive controls whether the current document is allowed to use the Gamepad API.
Specifically, where a defined policy blocks use of this feature, calls to Navigator.getGamepads() will throw a SecurityError DOMException. In addition, the gamepadconnected and gamepaddisconnected events will not fire.
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.
The default allowlist for gamepad is self.
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 Permissions Policy:
Permissions-Policy: gamepad=(self "https://example.com")
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 Permissions Policy:
Permissions-Policy: gamepad=(self)
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 See alsoRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4