Using render IPC to record RAPPOR metric ContentSettings.MixedScript.RanMixedScript

tools/metrics/rappor/rappor.xml

 <!--
 Copyright 2015 The Chromium Authors. All rights reserved.
 Use of this source code is governed by a BSD-style license that can be
 found in the LICENSE file.
 -->
 
 <rappor-configuration>
 <!--
 This file is used to generate a comprehensive list of Chrome rappor metrics
 along with a detailed description for each histogram. See the design doc at
@@ skipping 117 matching lines @@
 <rappor-metric name="ContentSettings.MixedScript.DisplayedShield"
     type="ETLD_PLUS_ONE">
   <owner>lgarron@chromium.org</owner>
   <summary>
     The eTLD+1 of a URL that displayed a mixed script shield. Note: this does
     *not* include pages with mixed scripts where the user has already clicked
     through the shield.
   </summary>
 </rappor-metric>
 
+<rappor-metric name="ContentSettings.MixedScript.RanMixedScript"
+    type="ETLD_PLUS_ONE">
+  <owner>lgarron@chromium.org</owner>
+  <summary>
+    The eTLD+1 of a URL that when mixed script actually ran.

[nasko, 2015/06/01 20:52:50]

The code will log the origin, not the eTLD+1, right? If we have
foo.bar.some.sub.domain.com, origin will include the full string, where eTLD
will be just domain.com.

[lgarron, 2015/06/01 20:57:04]

All RAPPOR metrics are actually recorded as eTLD+1 for the time being:
https://www.chromium.org/developers/design-documents/rappor

See uses of the the neatly named "GetDomainAndRegistrySampleFromGURL" function.

[nasko, 2015/06/01 21:07:02]

I think it isn't entirely reasonable to expect reviewers to read the design doc
for every CL.  Adding this bit of data on the comment of the
ContentRendererClient::RecordRapporURL interface will be fairly useful.

[lgarron, 2015/06/01 22:56:47]

The design doc isn't necessary, but anyone working with RAPPOR in Chrome will
presumably know this.
Also, the implementation of the convenience functions could be updated to report
different parts of the GURL (e.g. scheme, entire host).

[felt, 2015/06/12 00:32:51]

FWIW, I came into this file with the same question as Nasko. ("Isn't the code
logging the origin, not the eTLD+1?") I don't think it needs a code comment
because it's standard for RAPPOR metrics, but it would have been useful as a
note to the reviewer when the CL was mailed. :)

+  </summary>
+</rappor-metric>
+
 <rappor-metric name="ContentSettings.PermissionActions_Camera.Revoked.Url"
     type="ETLD_PLUS_ONE">
   <owner>jialiul@chromium.org</owner>
   <summary>
     The domain for which a camera permission was revoked.
   </summary>
 </rappor-metric>
 
 <rappor-metric name="ContentSettings.PermissionActions_Geolocation.Denied.Url"
     type="ETLD_PLUS_ONE">
@@ skipping 284 matching lines @@
   <owner>nparker@chromium.org</owner>
   <summary>
     The domain+registry of a URL that triggered an SSL interstitial.     Domains
     for bad-clock warnings are not reported.
   </summary>
 </rappor-metric>
 
 </rappor-metrics>
 
 </rappor-configuration>