A RetroSearch Logo

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

Search Query:

Showing content from https://developer.chrome.com/docs/extensions/reference/api/contentSettings below:

chrome.contentSettings | API | Chrome for Developers

Skip to main content chrome.contentSettings

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

Description

Use the chrome.contentSettings API to change settings that control whether websites can use features such as cookies, JavaScript, and plugins. More generally speaking, content settings allow you to customize Chrome's behavior on a per-site basis instead of globally.

Permissions

contentSettings

You must declare the "contentSettings" permission in your extension's manifest to use the API. For example:

{
  "name": "My extension",
  ...
  "permissions": [
    "contentSettings"
  ],
  ...
}
Concepts and usage Content setting patterns

You can use patterns to specify the websites that each content setting affects. For example, https://*.youtube.com/* specifies youtube.com and all of its subdomains. The syntax for content setting patterns is the same as for match patterns, with a few differences:

Pattern precedence

When more than one content setting rule applies for a given site, the rule with the more specific pattern takes precedence.

For example, the following patterns are ordered by precedence:

  1. https://www.example.com/*
  2. https://*.example.com/* (matching example.com and all subdomains)
  3. <all_urls> (matching every URL)

Three kinds of wildcards affect how specific a pattern is:

If a pattern is more specific than another pattern in one part but less specific in another part, the different parts are checked in the following order: hostname, scheme, port. For example, the following patterns are ordered by precedence:

  1. https://www.example.com:*/* Specifies the hostname and scheme.
  2. *:/www.example.com:123/* Not as high, because although it specifies the hostname, it doesn't specify the scheme.
  3. https://*.example.com:123/* Lower because although it specifies the port and scheme, it has a wildcard in the hostname.
Primary and secondary patterns

The URL taken into account when deciding which content setting to apply depends on the content type. For example, for contentSettings.notifications settings are based on the URL shown in the omnibox. This URL is called the "primary" URL.

Some content types can take additional URLs into account. For example, whether a site is allowed to set a contentSettings.cookies is decided based on the URL of the HTTP request (which is the primary URL in this case) as well as the URL shown in the omnibox (which is called the "secondary" URL).

If multiple rules have primary and secondary patterns, the rule with the more specific primary pattern takes precedence. If there multiple rules have the same primary pattern, the rule with the more specific secondary pattern takes precedence. For example, the following list of primary/secondary pattern pairs is ordered by precedence:

Precedence Primary pattern Secondary pattern 1 https://www.moose.com/*, https://www.wombat.com/* 2 https://www.moose.com/*, <all_urls> 3 <all_urls>, https://www.wombat.com/* 4 <all_urls>, <all_urls>

Secondary patterns are not supported for the images content setting.

Resource identifiers

Resource identifiers allow you to specify content settings for specific subtypes of a content type. Currently, the only content type that supports resource identifiers is contentSettings.plugins, where a resource identifier identifies a specific plugin. When applying content settings, first the settings for the specific plugin are checked. If there are no settings found for the specific plugin, the general content settings for plugins are checked.

For example, if a content setting rule has the resource identifier adobe-flash-player and the pattern <all_urls>, it takes precedence over a rule without a resource identifier and the pattern https://www.example.com/*, even if that pattern is more specific.

You can get a list of resource identifiers for a content type by calling the contentSettings.ContentSetting.getResourceIdentifiers() method. The returned list can change with the set of installed plugins on the user's machine, but Chrome tries to keep the identifiers stable across plugin updates.

Examples

To try this API, install the contentSettings API example from the chrome-extension-samples repository.

Types Properties Enum

"allow"

"block"

"session_only"

MultipleAutomaticDownloadsContentSetting

NotificationsContentSetting

PpapiBrokerContentSetting

Properties

Scope

The scope of the ContentSetting. One of regular: setting for regular profile (which is inherited by the incognito profile if not overridden elsewhere), incognito\_session\_only: setting for incognito profile that can only be set during an incognito session and is deleted when the incognito session ends (overrides regular settings).

Enum

"regular"

"incognito_session_only"

Properties

automaticDownloads

Whether to allow sites to download multiple files automatically. One of allow: Allow sites to download multiple files automatically, block: Don't allow sites to download multiple files automatically, ask: Ask when a site wants to download files automatically after the first file. Default is ask. The primary URL is the URL of the top-level frame. The secondary URL is not used.

autoVerify

Whether to allow sites to use the Private State Tokens API. One of allow: Allow sites to use the Private State Tokens API, block: Block sites from using the Private State Tokens API. Default is allow. When calling set(), the primary URL pattern must be <all_urls>. The secondary URL is not used.

camera

Whether to allow sites to access the camera. One of allow: Allow sites to access the camera, block: Don't allow sites to access the camera, ask: Ask when a site wants to access the camera. Default is ask. The primary URL is the URL of the document which requested camera access. The secondary URL is not used. NOTE: The 'allow' setting is not valid if both patterns are '<all_urls>'.

clipboard

Whether to allow sites to access the clipboard via advanced capabilities of the Async Clipboard API. "Advanced" capabilities include anything besides writing built-in formats after a user gesture, i.e. the ability to read, the ability to write custom formats, and the ability to write without a user gesture. One of allow: Allow sites to use advanced clipboard capabilities, block: Don't allow sites to use advanced clipboard capabilties, ask: Ask when a site wants to use advanced clipboard capabilities. Default is ask. The primary URL is the URL of the document which requested clipboard access. The secondary URL is not used.

cookies

Whether to allow cookies and other local data to be set by websites. One of allow: Accept cookies, block: Block cookies, session\_only: Accept cookies only for the current session. Default is allow. The primary URL is the URL representing the cookie origin. The secondary URL is the URL of the top-level frame.

fullscreen

Deprecated. No longer has any effect. Fullscreen permission is now automatically granted for all sites. Value is always allow.

images

Whether to show images. One of allow: Show images, block: Don't show images. Default is allow. The primary URL is the URL of the top-level frame. The secondary URL is the URL of the image.

javascript

Whether to run JavaScript. One of allow: Run JavaScript, block: Don't run JavaScript. Default is allow. The primary URL is the URL of the top-level frame. The secondary URL is not used.

location

Whether to allow Geolocation. One of allow: Allow sites to track your physical location, block: Don't allow sites to track your physical location, ask: Ask before allowing sites to track your physical location. Default is ask. The primary URL is the URL of the document which requested location data. The secondary URL is the URL of the top-level frame (which may or may not differ from the requesting URL).

microphone

Whether to allow sites to access the microphone. One of allow: Allow sites to access the microphone, block: Don't allow sites to access the microphone, ask: Ask when a site wants to access the microphone. Default is ask. The primary URL is the URL of the document which requested microphone access. The secondary URL is not used. NOTE: The 'allow' setting is not valid if both patterns are '<all_urls>'.

mouselock

Deprecated. No longer has any effect. Mouse lock permission is now automatically granted for all sites. Value is always allow.

notifications

Whether to allow sites to show desktop notifications. One of allow: Allow sites to show desktop notifications, block: Don't allow sites to show desktop notifications, ask: Ask when a site wants to show desktop notifications. Default is ask. The primary URL is the URL of the document which wants to show the notification. The secondary URL is not used.

plugins

Deprecated. With Flash support removed in Chrome 88, this permission no longer has any effect. Value is always block. Calls to set() and clear() will be ignored.

Whether to allow sites to show pop-ups. One of allow: Allow sites to show pop-ups, block: Don't allow sites to show pop-ups. Default is block. The primary URL is the URL of the top-level frame. The secondary URL is not used.

unsandboxedPlugins

Deprecated. Previously, controlled whether to allow sites to run plugins unsandboxed, however, with the Flash broker process removed in Chrome 88, this permission no longer has any effect. Value is always block. Calls to set() and clear() will be ignored.

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 2025-08-11 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 2025-08-11 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