Turn on auto-dismissing dialogs for trunk builds.

chrome/browser/ui/javascript_dialogs/javascript_dialog_tab_helper.cc

Index: chrome/browser/ui/javascript_dialogs/javascript_dialog_tab_helper.cc
diff --git a/chrome/browser/ui/javascript_dialogs/javascript_dialog_tab_helper.cc b/chrome/browser/ui/javascript_dialogs/javascript_dialog_tab_helper.cc
index 82b1781d9220090608f3cd250c16b6902be03c4e..e234e674efc4274fdefa27fe490b92bc39d97109 100644
--- a/chrome/browser/ui/javascript_dialogs/javascript_dialog_tab_helper.cc
+++ b/chrome/browser/ui/javascript_dialogs/javascript_dialog_tab_helper.cc
@@ -24,7 +24,11 @@ DEFINE_WEB_CONTENTS_USER_DATA_KEY(JavaScriptDialogTabHelper);
 namespace {
 
 bool IsEnabled() {
+#if defined(GOOGLE_CHROME_BUILD)
   return base::FeatureList::IsEnabled(features::kAutoDismissingDialogs);
+#else
+  return true;
+#endif

[nasko, 2017/03/28 17:29:19]

It isn't very obvious, but the right way to enable it is to change
testing/variations/fieldtrial_testing_config.json and add your field trial as
enabled. This will turn it on for all chromium builds, including trunk and
waterfall. Once you are comfortable you no longer need field trial code, you
just rip it all out.

[Avi (use Gerrit), 2017/03/28 19:58:51]

The more you know...

(how do you know this?)

 }
 
 app_modal::JavaScriptDialogManager* AppModalDialogManager() {