Added a ForceYouTubeRestrict policy and deprecated the old ForceYouTubeSafetyMode policy

chrome/common/pref_names.cc

Index: chrome/common/pref_names.cc
diff --git a/chrome/common/pref_names.cc b/chrome/common/pref_names.cc
index 2ecbec2f7e247ea31e4b2400185547ab831999d3..31e4c522648e117d5ff7135d0f724dd3793b4bb2 100644
--- a/chrome/common/pref_names.cc
+++ b/chrome/common/pref_names.cc
@@ -921,8 +921,9 @@ const char kAllowDeletingBrowserHistory[] = "history.deleting_enabled";
 // Boolean controlling whether SafeSearch is mandatory for Google Web Searches.
 const char kForceGoogleSafeSearch[] = "settings.force_google_safesearch";
 
-// Boolean controlling whether Safety Mode is mandatory on YouTube.
-const char kForceYouTubeSafetyMode[] = "settings.force_youtube_safety_mode";
+// Integer controlling whether Restrict Mode (moderate/strict) is mandatory on

[Thiemo Nagel, 2016/10/05 17:38:14]

Nit: I'd suggest "mandatory on" --> "applied to".

[ljusten (tachyonic), 2016/10/06 10:14:45]

I'd like to keep it this way. 'Mandatory' is stronger and hints that strict
settings overrule potential less strict settings elsewhere, e.g. in YouTube
settings. It's also consistent with the lingo for safe search.

+// YouTube. See |safe_search_util::YouTubeRestrictMode| for possible values.
+const char kForceYouTubeRestrict[] = "settings.force_youtube_restrict";
 
 // Boolean controlling whether history is recorded via Session Sync
 // (for supervised users).