Commit e2b4d431 authored by Guillaume Jenkins's avatar Guillaume Jenkins Committed by Commit Bot

[Policy] Move DisableSafeBrowsingProceedAnyway to future_on

Moves the DisableSafeBrowsingProceedAnyway from supported_on iOS 85 to
future_on. This is the only policy that wasn't moved to future_on, other
than EnableExperimentalPolicies. I believe it was an oversight. Without
this change, the enterprise documentation page for the policy has a
visual bug when displaying supported versions:

https://screenshot.googleplex.com/7ZxKRy3mCmgCyut

BYPASS_POLICY_COMPATIBILITY_CHECK="Moving the policy to future_on, since it hasn't truly been released"

Bug: 1129888
Change-Id: I215afe151edc7379b60c85dcf2e1b31be00d625c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2416852
Commit-Queue: Guillaume Jenkins <gujen@google.com>
Reviewed-by: default avatarOwen Min <zmin@chromium.org>
Reviewed-by: default avatarJulian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#808385}
parent 1e32efc6
...@@ -10111,9 +10111,9 @@ ...@@ -10111,9 +10111,9 @@
'supported_on': [ 'supported_on': [
'chrome.*:22-', 'chrome.*:22-',
'chrome_os:22-', 'chrome_os:22-',
'android:30-', 'android:30-'
'ios:85-'
], ],
'future_on': ['ios'],
'features': { 'features': {
'dynamic_refresh': True, 'dynamic_refresh': True,
'per_profile': True, 'per_profile': True,
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment