Integration and Permissions
Related: storage
Permissions may be (temporarily) rejected or (temporarily or permanently) granted. The exact capabilities regarding permissions may depend on the browser. [chrome-dev]
User Activation
Related: UI interaction
Certain functionality or permissions are only allowed in response to user activation. For example, the clipboard cannot be written into without any user interaction. And there are many more APIs which require a user activation before they can be used. A user activation can be triggered, for example, by a click or a keyboard event. There is a distinction between transient and sticky activation. [MDN, spec, MDN, webkit.org]
Permission Policy
Related: content security policy
The Permission-Policy HTTP header provides a mechanism to allow and deny the use of browser features in a document or within any
[MDN,
w3c/webappsec-permissions-policy,
w3c/webappsec-permissions-policy,
chrome-dev].<iframe> elements in the document
There is currently no easy way to disable all current and future policies [paul.kinlan.me].
Files
The File System Access API allows read, write, and file management capabilities. Some browsers also support folder access. [MDN]
Fullscreen
The Fullscreen API allows to put a whole website—or only a specific element and its children—into a fullscreen mode where the browser may hide all or some parts of its user interface. The API also allows to exit fullscreen and to detect whether the browser even allows fullscreen. [MDN]
Hitting escape on the keyboard usually cancels the fullscreen mode. This behaviour can be avoided using the Keyboard Lock APi. [MDN]