Use the ntextMenus API to add items to Google Chrome's context menu. More generally speaking, content settings allow you to customize Chrome's behavior on a per-site basis instead of globally. Use the ntentSettings API to change settings that control whether websites can use features such as cookies, JavaScript, and plugins. Use the commands API to add keyboard shortcuts that trigger actions in your extension, for example, an action to open the browser action or send a command to the extension.

Use this API to expose certificates to the platform which can use these certificates for TLS authentications. Note that accessibilityFeatures.modify does not imply accessibilityFeatures.read permission. For modifying feature state, the extension needs accessibilityFeatures.modify permission. In order to get feature states the extension must request accessibilityFeatures.read permission. This API relies on the ChromeSetting prototype of the type API for getting and setting individual accessibility features. Use the chrome.accessibilityFeatures API to manage Chrome's accessibility features. Release information is not available for APIs before Chrome 42, which was released in early 2015. For more information, see Asynchronous methods. If you need to know the result of calling such methods, use the returned promise or pass a callback function into the method. Unless stated otherwise, methods in the chrome.* APIs are asynchronous: they return immediately, without waiting for the operation to finish. If your extension requires a specific API, you can specify a minimum chrome version in the manifest file. For extension features added in later Chrome versions, see the API reference documentation for support information.

Manifest V3 is supported generally in Chrome 88 or later.

Remote desktop manager chrome extension