Revamp the Incognito NTP on Desktop

chrome/browser/about_flags.cc

Index: chrome/browser/about_flags.cc
diff --git a/chrome/browser/about_flags.cc b/chrome/browser/about_flags.cc
index d52f7355119297e2b95d40f09d3b034f4e81b4cd..115cb06d31834a1f34f0ec20a442f7ec6968efc7 100644
--- a/chrome/browser/about_flags.cc
+++ b/chrome/browser/about_flags.cc
@@ -1975,6 +1975,10 @@ const FeatureEntry kFeatureEntries[] = {
     {"enable-md-history", flag_descriptions::kEnableMaterialDesignHistoryName,
      flag_descriptions::kEnableMaterialDesignHistoryDescription, kOsDesktop,
      FEATURE_VALUE_TYPE(features::kMaterialDesignHistory)},
+    {"enable-md-incognito-ntp",

[Dan Beam, 2017/04/20 18:27:51]

fwiw: the new tab page is already material design...

if we really end up needing a feature/flag, maybe
--enable-responsive-incognito-ntp maybe?

probably doesn't matter, but it might be a little confusing

[msramek, 2017/04/21 12:20:36]

I know that the native tab UI has been materialized, but the Incognito tab
content was previously not conforming to the MD style guide (or so I was told).
We don't have a flag for MD NTP in general, so I hope this wouldn't be
confusing, and it will nicely fit with the other MD flags.

I also want to reuse the flag on Android, where "responsive" might be more
confusing, since you don't typically resize the browser window there.

And the flag is hopefully shortlived. So I would prefer to keep the name.

+     flag_descriptions::kMaterialDesignIncognitoNTPName,
+     flag_descriptions::kMaterialDesignIncognitoNTPDescription, kOsDesktop,
+     FEATURE_VALUE_TYPE(features::kMaterialDesignIncognitoNTP)},
     {"enable-md-settings", flag_descriptions::kEnableMaterialDesignSettingsName,
      flag_descriptions::kEnableMaterialDesignSettingsDescription, kOsDesktop,
      FEATURE_VALUE_TYPE(features::kMaterialDesignSettings)},