Add filesystem scheme to navigation histograms.

components/navigation_metrics/navigation_metrics.cc

Index: components/navigation_metrics/navigation_metrics.cc
diff --git a/components/navigation_metrics/navigation_metrics.cc b/components/navigation_metrics/navigation_metrics.cc
index e4c8ed5374942953c8a17cbc9a445471c60affc6..58ae7d033f27be4d4e311b48c909dc1856371946 100644
--- a/components/navigation_metrics/navigation_metrics.cc
+++ b/components/navigation_metrics/navigation_metrics.cc
@@ -23,21 +23,23 @@ enum Scheme {
   SCHEME_ABOUT,
   SCHEME_CHROME,
   SCHEME_BLOB,
+  SCHEME_FILESYSTEM,
   SCHEME_MAX,
 };
 
 const char* const kSchemeNames[] = {
-  "unknown",
-  url::kHttpScheme,
-  url::kHttpsScheme,
-  url::kFileScheme,
-  url::kFtpScheme,
-  url::kDataScheme,
-  url::kJavaScriptScheme,
-  url::kAboutScheme,
-  "chrome",
-  url::kBlobScheme,
-  "max",
+    "unknown",
+    url::kHttpScheme,
+    url::kHttpsScheme,
+    url::kFileScheme,
+    url::kFtpScheme,
+    url::kDataScheme,
+    url::kJavaScriptScheme,
+    url::kAboutScheme,
+    "chrome",
+    url::kBlobScheme,
+    url::kFileSystemScheme,
+    "max",

[Ilya Sherman, 2016/11/04 18:34:30]

nit: By the way, I don't think the indentation adjustment here is correct.  Is
this a result of "git cl format", or a manual edit?  (If it's git cl format,
then it might be worth filing a git cl format bug, but mostly you can ignore my
comment.)

[meacer, 2016/11/04 19:11:46]

I used git cl format. Should the correct indentation be 2 spaces? It looks like
there is existing 4 space examples in the codebase too:
https://cs.chromium.org/chromium/src/net/dns/mdns_client_unittest.cc?q=k%5Ba-...

[Ilya Sherman, 2016/11/05 00:29:00]

Yeah, I would have expected 2 spaces.  But, if this is git cl format output,
it's probably not worth worrying about too much.  Thanks!

 };
 
 static_assert(arraysize(kSchemeNames) == SCHEME_MAX + 1,