DefaultBrowserWorker now fully supports opening the settings for Win10

tools/metrics/histograms/histograms.xml

Index: tools/metrics/histograms/histograms.xml
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml
index 660df62d1f43ecd49f3bddef693bb5d0a2480bea..240f644d528eb9dfa86d5c1e02d2bd46418ee671 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -7646,6 +7646,26 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
   </summary>
 </histogram>
 
+<histogram name="DefaultBrowser.SettingsInteraction.ConcludeReason"
+    enum="SettingsInteractionConcludeReason">
+  <owner>pmonette@chromium.org</owner>
+  <summary>
+    The reason why the default browser settings interaction concluded on Windows
+    10.
+  </summary>
+</histogram>
+
+<histogram name="DefaultBrowser.SettingsInteraction.RegistryWatcherDuration"
+    units="ms">
+  <owner>pmonette@chromium.org</owner>
+  <summary>
+    The registry keys for the default browser protocols (http/https) are
+    monitored to know when the user finished interacting with the system
+    settings. This is how long it took for the last registry watcher to get
+    signaled.
+  </summary>
+</histogram>
+
 <histogram name="DefaultBrowser.State" enum="DefaultBrowserState">
   <owner>gab@chromium.org</owner>
   <summary>Whether Chrome was the default browser when it started up.</summary>
@@ -82648,6 +82668,15 @@ To add a new entry, add it with any value and run test to compute valid value.
   </int>
 </enum>
 
+<enum name="SettingsInteractionConcludeReason" type="int">
+  <int value="0" label="Registry watcher">
+    A change to the protocol registry key was detected.
+  </int>
+  <int value="1" label="Timeout">
+    The timer fired before a change to the protocol registry key was detected.
+  </int>
+</enum>
+
 <enum name="SettingsSections" type="int">
   <summary>
     A collection of sections from chrome://settings. Used for metrics about