Raw Clipboard: Add to Bad Flags to add a warning.

Add kRawClipboard to the bad flags list.

This will allow the dev trial to continue, but with a clear indicator
of a dangerous API being exposed.

Bug: 897289
Change-Id: I401d01a884d653caa50b767f118edf136ce99a95
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2086011Reviewed-by: Tommy Martino <tmartino@chromium.org>
Commit-Queue: Darwin Huang <huangdarwin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#746899}

chrome/browser/ui/startup/bad_flags_prompt.cc

@@ -38,6 +38,7 @@
 #include "media/media_buildflags.h"
 #include "services/network/public/cpp/network_switches.h"
 #include "services/service_manager/sandbox/switches.h"
+#include "third_party/blink/public/common/features.h"
 #include "ui/base/l10n/l10n_util.h"
 #include "ui/base/resource/resource_bundle.h"
 
@@ -141,6 +142,7 @@ static const char* kBadFlags[] = {
 // Dangerous feature flags in about:flags for which to display a warning that
 // "stability and security will suffer".
 static const base::Feature* kBadFeatureFlagsInAboutFlags[] = {
+    &blink::features::kRawClipboard,
     &features::kAllowSignedHTTPExchangeCertsWithoutExtension,
     &features::kWebBundlesFromNetwork,
 #if defined(OS_ANDROID)