Add experimental feature info to certificate reports

components/certificate_reporting/error_report.h

 // 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.
 
 #ifndef COMPONENTS_CERTIFICATE_REPORTING_CERTIFICATE_ERROR_REPORT_H_
 #define COMPONENTS_CERTIFICATE_REPORTING_CERTIFICATE_ERROR_REPORT_H_
 
+#include <map>
 #include <memory>
 #include <string>
 
+namespace base {
+struct Feature;
+}  // namespace base
 
 namespace net {
 class SSLInfo;
 }  // namespace net
 
 namespace certificate_reporting {
 
 class CertLoggerRequest;
 
 // This class builds and serializes reports for invalid SSL certificate
@@ skipping 36 matching lines @@
   // successful and false otherwise.
   bool Serialize(std::string* output) const;
 
   void SetInterstitialInfo(const InterstitialReason& interstitial_reason,
                            const ProceedDecision& proceed_decision,
                            const Overridable& overridable);
 
   // Gets the hostname to which this report corresponds.
   const std::string& hostname() const;
 
+  // Populates the report with information about the given feature,
+  // including whether it is enabled or disabled and its experiment
+  // parameters.
+  void AddFeature(const std::string& feature_name,
+                  bool enabled,
+                  const std::map<std::string, std::string>& params);

[jwd, 2016/11/03 15:15:34]

Hmmm, I actually liked passing the feature itself more. I was thinking of
passing a list of the param keys, letting AddFeature get the values based on the
given feature. Thoughts?

+
  private:
   std::unique_ptr<CertLoggerRequest> cert_report_;
 };
 
 }  // namespace certificate_reporting
 
 #endif  // COMPONENTS_CERTIFICATE_REPORTING_CERTIFICATE_ERROR_REPORT_H_