Brave Browser: 1.94.121 to 1.96.60

This policy can be used to allow Chrome DevTools on specific URLs. [added: Chrome DevTools availability is evaluated at the target level. ]URL patterns are matched against the URL of [removed: every][added: each target being inspected (such as the main] frame [removed: on the page being inspected.][added: of a page, an embedded subframe, an extension, or a web application).] The resulting behavior depends on whether the DeveloperToolsAvailabilityBlocklist policy is also set. If this policy is set and DeveloperToolsAvailabilityBlocklist is not, [removed: every frame's][added: a target's] URL must match a pattern on this allowlist for Chrome DevTools to be [removed: allowed.][added: allowed for that target.] If [removed: any frame's][added: a target's] URL does not [removed: match,][added: match this allowlist, Chrome] DevTools will be blocked for [added: that target (for example, a subframe whose URL is not on ]the [removed: entire page.][added: allowlist cannot be inspected, but the main page remains inspectable if its URL is allowlisted).] For information on the URL format, see https://support.google.com/chrome/a?p=url_blocklist_filter_format. If both this and the DeveloperToolsAvailabilityBlocklist policies are set, this allowlist takes precedence. If a [removed: frame's][added: target's] URL matches a pattern on this allowlist, it will be allowed, even if it also matches a pattern in the blocklist. If a [added: target's ]URL matches a pattern on the blocklist (but not the allowlist), it will be blocked. If a [added: target's ]URL matches neither, the DeveloperToolsAvailability policy will be used as a fallback. If this policy is not set, the availability of Chrome DevTools is determined by the DeveloperToolsAvailabilityBlocklist and DeveloperToolsAvailability policies.[removed: This policy also applies to Chrome DevTools opened for extensions and web applications.] Blanket host wildcards (i.e., "*" or "[*]") are not allowed; use the DeveloperToolsAvailability policy to enable the feature globally. This policy is limited to 1,000 entries. Example value: example.com https://ssl.server.com hosting.com/bad_path https://server:8080/path .exact.hostname.com file://*

This policy can be used to block Chrome DevTools on specific URLs. For information on the URL format, see https://support.google.com/chrome/a?p=url_blocklist_filter_format. [added: Chrome DevTools availability is evaluated at the target level. ]URL patterns are matched against the URL of [removed: every][added: each target being inspected (such as the main] frame [removed: on the page being inspected.][added: of a page, an embedded subframe, an extension, or a web application).] The resulting behavior depends on whether the DeveloperToolsAvailabilityAllowlist policy is also set. If this policy is set and DeveloperToolsAvailabilityAllowlist is not, [removed: any frame's][added: a target's] URL matching a pattern on this blocklist will block Chrome DevTools for [added: that target (for example, a subframe whose URL matches this blocklist cannot be inspected, but ]the [removed: entire page.][added: main page remains inspectable if its URL is not blocklisted).] If a [removed: frame's][added: target's] URL does[removed: n'][added: no]t match any pattern, the availability is determined by the DeveloperToolsAvailability policy. If both this and the DeveloperToolsAvailabilityAllowlist policies are set, the allowlist takes precedence. If a [removed: frame's][added: target's] URL matches a pattern on the allowlist, it will be allowed, even if it also matches a pattern in this blocklist. If a [added: target's ]URL matches a pattern on this blocklist (but not the allowlist), it will be blocked. If a[added: target's] URL matches neither, the DeveloperToolsAvailability policy will be used as a fallback. If this policy is not set, the availability of Chrome DevTools is determined by the DeveloperToolsAvailabilityAllowlist and DeveloperToolsAvailability policies. This policy is limited to 1,000 entries. Example value: https://example.com example.com https://ssl.server.com hosting.com/bad_path https://server:8080/path .exact.hostname.com * file://*

When this policy is set to Enabled, Local Network Access requests will only display warnings in Chrome DevTools due to Local Network Access checks failing. When this policy is set to Disabled or unset, Local Network Access requests will use the default handling of these requests. See https://wicg.github.io/local-network-access/ for Local Network Access restrictions. This enterprise policy is temporary, and will be removed after M1[removed: 56][added: 63]. Long term, the policy LocalNetworkAccessAllowedForUrls can be used to allowlist URL patterns that should be automatically granted the Local Network Access permission.

List of URL patterns. Network requests initiated from websites served by matching origins are not subject to Local Network Access checks. For origins not covered by the patterns specified here, the user's personal configuration will apply. For detailed information on valid URL patterns, please see https://chromeenterprise.google/policies/url-patterns/. See https://wicg.github.io/local-network-access/ for Local Network Access restrictions. There are multiple policies listing origins that impact requests to local device and local network endpoints. If an origin is matched by more than one of the following policies, the policies take precedence in the following order: - LocalNetworkBlockedForUrls - LocalNetworkAllowedForUrls - LoopbackNetwork[removed: Access]BlockedForUrls - LoopbackNetworkA[removed: ccessA]llowedForUrls - LocalNetworkAccessBlockedForUrls - LocalNetworkAccessAllowedForUrls Example value: http://www.example.com:8080 [*.]example.edu *

List of URL patterns. Network requests initiated from websites served by matching origins are blocked from issuing Local Network Access requests. For origins not covered by the patterns specified here, the user's personal configuration will apply. For detailed information on valid URL patterns, please see https://chromeenterprise.google/policies/url-patterns/. See https://wicg.github.io/local-network-access/ for Local Network Access restrictions. There are multiple policies listing origins that impact requests to local device and local network endpoints. If an origin is matched by more than one of the following policies, the policies take precedence in the following order: - LocalNetworkBlockedForUrls - LocalNetworkAllowedForUrls - LoopbackNetwork[removed: Access]BlockedForUrls - LoopbackNetworkA[removed: ccessA]llowedForUrls - LocalNetworkAccessBlockedForUrls - LocalNetworkAccessAllowedForUrls Example value: http://www.example.com:8080 [*.]example.edu *

If the policy is set to false, the New Tab page won't allow users to customize the background. Any existing custom background will be permanently removed even if the policy is set to true later. If the policy is set to true or unset, users can customize the background on the New Tab page.[added: Note: On Android, the policy is applied to browser only after restart.]