Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://developer.chrome.com/docs/extensions/develop/concepts/permission-warnings below:

Permission warning guidelines | Chrome Extensions

Stay organized with collections Save and categorize content based on your preferences.

Chrome extensions enhance the user's browser experience. To do this extensions use Chrome APIs that require certain permissions. Some permissions are less intrusive and don't display a warning. Other permissions trigger a warning that users have to allow. This page provides guidelines for working with permission warnings. Specific warnings are noted in the Permissions under the permission to which they apply.

When a new permission that triggers a warning is added, the extension will be disabled until the user accepts the new permission. See Updating permissions to learn how to test this behavior.

Some permissions may not display warnings when paired with other permissions. For example, the "tabs" warning won't show if the extension also requests "<all_urls>".

Permission warnings describe the capabilities an API grants, but some warnings are harder to understand than others. Users are more likely to install extensions that follow these guidelines:

Request relevant permissions

Extensions are required to fulfill a single purpose and comply with the Use of permissions policy. Ensure you only request permissions that support the extension's main functionality.

Use optional permissions

Improve the onboarding experience by requesting permissions at runtime. This lets you provide more context around a particular permission and lets users choose which features they want to enable. See Permissions API for implementation details.

Use the "activeTab" permission

This permission does not display a permission warning. It grants temporary host permission to the site the user is on. For details, see Understanding the activeTab permission.

To view an extension's permission warnings, you have the following options:

Before you begin

1. Install Node.js and NPM.
2. Install Chromium.
3. Clone the extension-update-testing-tool repository.
4. Run npm install in the root of the repository.

Using the tool

1. Run npm start.
2. Open the local server at http://localhost:8080 in Chromium.
3. Drag an unpacked extension (folder or .zip file) to the page.
4. Follow the instructions under "Install manually" to download and install the extension.

1. Navigate to chrome://extensions
2. Enable developer mode
3. Click Pack Extension. Figure 3: Developer mode enabled in the Extension management page
4. Specify the path to the extension's folder in the extension root directory field. Ignore the Private key field for a first-time package.

5. Click the Pack Extension button.

   Figure 4: Specifying Extension Path

6. Chrome will create two files, a .crx file and a .pem file. The .pem file contains the private key used to sign the extension. Make sure you remember which directory these files were saved.

   Figure 5: Packaged Extension Files

7. Keep the .pem file in a secret and secure place; it will be needed to update the extension.

8. Install the .crx file by dropping it into the Extension's Management page.

   Figure 6: Drop file to install

9. After dropping the .crx file the browser will ask if the extension can be added and display warnings.

   Figure 7: Warning for New Tab extension

When an extension adds a new permission that triggers a warning it may temporarily disable it. The extension will be re-enabled only after the user agrees to accept the new permission.

To check if your extension will be disabled when adding a new permission, you have the following options:

These steps assume you followed the Using the Extension Update Testing Tool instructions to start the server.

Using the tool

1. Add a new permission with warning.
2. Increase the extension version number.
3. Drag the unpacked extension (folder or .zip file) to the page.
4. Go to chrome://extensions.
5. Click the Update button.

1. Find the .crx file you just created in View Warnings.
2. Rename it or delete it.
3. Open your manifest.json and add any permission that triggers a warning.
4. Go to chrome://extensions. Do not remove the previously installed package.
5. Pack the extension again, but this time add the pem file in the second input. Figure 8: Packing extension dialog with pem file included.
6. Drag the new packaged extension to the Extension Management page.

7. You will see a dialog that prompts the user to accept the new permissions.

   Figure 9: Disabled extension warning Figure 10: Requesting new permission dialog

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2024-02-05 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-02-05 UTC."],[],[]]

RetroSearch 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