Wire up a way for users to disable particular kinds of reporting.

Author: jyasskin

index.src.html

@@ -289,6 +289,13 @@ <h4 id="concept-reports">Reports</h4>
   counter, which is a non-negative integer representing the number of times the
   user agent attempted to deliver the report.
 
+  <h4 id="concept-configuration">User configuration</h4>
+
+  Reporting may be <dfn for="reporting">disabled</dfn> for particular [=report
+  types=], potentially on particular [=origins=]. The specification does not
+  define how [=/user agents=] determine whether their users prefer to disable
+  reporting.
+
   <h3 id="media-type">Media Type</h3>
 
   The media type used when POSTing reports to a specified endpoint is
@@ -493,6 +500,9 @@ <h4 id="generate-report" export algorithm>Generate report of |type| with
 
   1.  Let |settings| be |context|'s [=relevant settings object=].
 
+  1.  If reporting is [=reporting/disabled=] for |type| and |settings|'
+      [=environment settings object/origin=], return.
+
   2.  Let |report| be the result of running [=generate a report=] with |data|,
       |type|, |destination| and |settings|.
 
@@ -1086,8 +1096,8 @@ <h3 id="disable">Disabling Reporting</h3>
   Sending reports costs bandwidth, and potentially could reveal some small
   amount of additional information above and beyond what a website can obtain
   in-band ([[NETWORK-ERROR-LOGGING]], for instance). User agents MUST allow
-  users to disable reporting with some reasonable amount of granularity in order
-  to maintain the priority of constituencies espoused in
+  users to [=reporting/disabled|disable reporting=] with some reasonable amount
+  of granularity in order to maintain the priority of constituencies espoused in
   [[HTML-DESIGN-PRINCIPLES]].
 </section>