DialogBrowserTest implementation to invoke Content settings bubble dialogs.

chrome/browser/ui/test/browser_dialog_browsertest.cc

Index: chrome/browser/ui/test/browser_dialog_browsertest.cc
diff --git a/chrome/browser/ui/test/browser_dialog_browsertest.cc b/chrome/browser/ui/test/browser_dialog_browsertest.cc
index 2c769d3b28b6081501ef2d977d440cf41e9a9cd4..f2188d4850409fb49e5f0640101f294091d8626a 100644
--- a/chrome/browser/ui/test/browser_dialog_browsertest.cc
+++ b/chrome/browser/ui/test/browser_dialog_browsertest.cc
@@ -8,6 +8,7 @@
 #include "base/test/test_switches.h"
 #include "base/test/test_timeouts.h"
 #include "chrome/browser/ui/test/test_browser_dialog.h"
+#include "content/public/common/content_switches.h"
 #include "testing/gtest/include/gtest/gtest.h"
 #include "ui/compositor/compositor_switches.h"
 
@@ -66,6 +67,11 @@ TEST(BrowserDialogTest, Invoke) {
     command.AppendSwitchASCII(switches::kTestLauncherTimeout,
                               TestTimeouts::kNoTimeoutSwitchValue);
     command.AppendSwitch(switches::kEnablePixelOutputInTests);
+#if defined(OS_WIN)
+    // Under Windows, pass in --disable-gpu for now due to
+    // http://crbug.com/687387.

[tapted, 2017/02/03 00:35:39]

There was a chromium-dev thread lately about not just citing bugs, but ensuring
there is enough context as well. E.g., the comment should mention something like

// Under Windows, dialogs (but not the browser window) created in the
// spawned browser_test process are invisible for an unknown reason. Pass
// --disable-gpu to resolve this for now. See http://crbug.com/687387.

[kylix_rd, 2017/02/03 18:55:03]

LOL! I just got nailed by my own pet-peeve... ;) Citing a bug reference only
without any summary context. Silly me.

[kylix_rd, 2017/02/03 18:55:03]

Done.

+    command.AppendSwitch(switches::kDisableGpu);
+#endif
   } else {
     options.wait = true;
   }