arc_support: This policy also controls access to Android Developer Options. If you set
  this policy to 'DeveloperToolsDisallowed' (value 2), users cannot access
  Developer Options. If you set this policy to another value or leave it
  unset, users can access Developer Options by tapping seven times on the
  build number in the Android settings app.
caption: Control where Developer Tools can be used
desc: |-
  Setting the policy to 0 (the default) means you can access the developer tools and the JavaScript console, but not in the context of extensions installed by enterprise policy or, since version 114 and if this is a managed user, extensions built into the browser. Setting the policy to 1 means you can access the developer tools and the JavaScript console in all contexts, including that of extensions installed by enterprise policy. Setting the policy to 2 means you can't access developer tools, and you can't inspect website elements.

  This setting also turns off keyboard shortcuts and menu or context menu entries to open developer tools or the JavaScript console.

  As of <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> version 99, this setting also controls entry points for the 'View page source' feature. If you set this policy to 'DeveloperToolsDisallowed' (value 2), users cannot access source viewing via keyboard shortcut or the context menu. To fully block source viewing, you must also add 'view-source:*' to the <ph name="URL_BLOCKLIST_POLICY_NAME">URLBlocklist</ph> policy.

  As of <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> version 119, this setting also controls whether developer mode for Isolated Web Apps can be activated and used.

  As of <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> version 128, this setting will not control developer mode on extensions page if <ph name="EXTENSION_DEVELOPER_MODE_SETTINGS_POLICY_NAME">ExtensionDeveloperModeSettings</ph> policy is set.

  The availability of Developer Tools is determined in the following order of precedence:
  1. If a URL matches a pattern in the <ph name="DEVELOPER_TOOLS_AVAILABILITY_ALLOWLIST_POLICY_NAME">DeveloperToolsAvailabilityAllowlist</ph> policy, Developer Tools are allowed.
  2. If the <ph name="DEVELOPER_TOOLS_AVAILABILITY_ALLOWLIST_POLICY_NAME">DeveloperToolsAvailabilityAllowlist</ph> is set and the <ph name="DEVELOPER_TOOLS_AVAILABILITY_BLOCKLIST_POLICY_NAME">DeveloperToolsAvailabilityBlocklist</ph> is not, any URL not on the allowlist is blocked.
  3. If a URL matches a pattern in the <ph name="DEVELOPER_TOOLS_AVAILABILITY_BLOCKLIST_POLICY_NAME">DeveloperToolsAvailabilityBlocklist</ph> policy, Developer Tools are blocked.
  4. If a URL is not covered by the allowlist or blocklist, this policy (<ph name="DEVELOPER_TOOLS_AVAILABILITY_POLICY_NAME">DeveloperToolsAvailability</ph>) is the fallback.
default: 0
example_value: 2
features:
  dynamic_refresh: true
  per_profile: true
future_on:
- fuchsia
items:
- caption: Disallow usage of the Developer Tools on apps and extensions
    installed by enterprise policy or, since version 114 and if this is a
    managed user, extensions built into the browser. Allow usage of the
    Developer Tools in other contexts
  name: DeveloperToolsDisallowedForForceInstalledExtensions
  value: 0
- caption: Allow usage of the Developer Tools
  name: DeveloperToolsAllowed
  value: 1
- caption: Disallow usage of the Developer Tools
  name: DeveloperToolsDisallowed
  value: 2
owners:
- file://extensions/OWNERS
- extensions-core@chromium.org
schema:
  enum:
  - 0
  - 1
  - 2
  type: integer
supported_on:
- chrome.*:68-
- chrome_os:68-
- android:154-
tags: []
type: int-enum
