Content Settings

Contents

1. Manifest
   1. h3Name
2. Content setting patterns
   1. Pattern precedence
3. Primary and secondary patterns
   1. h3Name
4. Resource identifiers
   1. h3Name
5. Examples
   1. h3Name
6. API reference: chrome.contentSettings
   1. Properties
      1. cookies
      2. images
      3. javascript
      4. plugins
      5. popups
      6. notifications
   2. Methods
      1. methodName
   3. Events
      1. eventName
   4. Types
      1. ResourceIdentifier
         1. Methods
            1. methodName
         2. Events
            1. eventName
      2. ContentSetting
         1. Methods
            1. clear
            2. get
            3. getResourceIdentifiers
            4. set
         2. Events
            1. eventName

The content settings module allows you to change settings that control whether websites can use features such as cookies, JavaScript, and plug-ins. More generally speaking, content settings allow you to customize Chrome's behavior on a per-site basis instead of globally.

Manifest

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

{
  "name": "My extension",
  ...
  "permissions": [
    "contentSettings"
  ],
  ...
}

Content setting patterns

You can use patterns to specify the websites that each content setting affects. For example, http://*.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:

• For http, https, and ftp URLs, the path must be a wildcard (/*). For file URLs, the path must be completely specified and must not contain wildcards.
• In contrast to match patterns, content setting patterns can specify a port number. If a port number is specified, the pattern only matches websites with that port. If no port number is specified, the pattern matches all ports.

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. http://www.example.com/*
2. http://*.example.com/* (matching example.com and all subdomains)
3. <all_urls> (matching every URL)

Three kinds of wildcards affect how specific a pattern is:

• Wildcards in the port (for example http://www.example.com:*/*)
• Wildcards in the scheme (for example *://www.example.com:123/*)
• Wildcards in the hostname (for example http://*.example.com:123/*)

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. http://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. http://*.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 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 cookie 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:

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 plugins, where a resource identifier identifies a specific plug-in. When applying content settings, first the settings for the specific plug-in are checked. If there are no settings found for the specific plug-in, the general content settings for plug-ins 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 http://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 getResourceIdentifiers() method. The returned list can change with the set of installed plug-ins on the user's machine, but Chrome tries to keep the identifiers stable across plug-in updates.

Examples

You can find samples of this API on the sample page.