Remove deprecation reports from main spec

Author: clelland

index.src.html

@@ -1136,91 +1136,6 @@ <h3 id="invoke-observers" algorthm>
         exception</a>.
 </section>
 
-<section>
-  <h2 id="report-types">Report Types</h2>
-
-  <h3 id="deprecation-report">Deprecation</h3>
-
-  <dfn>Deprecation reports</dfn> indicate that a browser API or feature has been
-  used which is expected to stop working in a future update to the browser.
-
-  <a>Deprecation reports</a> have the <a>report type</a> "deprecation".
-
-  <a>Deprecation reports</a> are <a>visible to
-  <code>ReportingObserver</code>s</a>.
-
-  <pre class="idl">
-    [Exposed=(Window,Worker)]
-    interface DeprecationReportBody : ReportBody {
-      [Default] object toJSON();
-      readonly attribute DOMString id;
-      readonly attribute Date? anticipatedRemoval;
-      readonly attribute DOMString message;
-      readonly attribute DOMString? sourceFile;
-      readonly attribute unsigned long? lineNumber;
-      readonly attribute unsigned long? columnNumber;
-    };
-  </pre>
-
-  A <a>deprecation report</a>'s [=report/body=], represented in JavaScript by
-  {{DeprecationReportBody}}, contains the following fields:
-
-    - <dfn for="DeprecationReportBody">id</dfn>: an implementation-defined
-      string identifying the feature or API that will be removed. This string
-      can be used for grouping and counting related reports.
-
-    - <dfn for="DeprecationReportBody">anticipatedRemoval</dfn>: A
-      JavaScript <a>Date object</a> (rendered as an ISO 8601 string) indicating
-      roughly when the browser version without the specified API will be
-      generally available (excluding "beta" or other pre-release channels). This
-      value should be used to sort or prioritize warnings. If unknown, this
-      field should be null, and the deprecation should be considered low
-      priority (removal may not actually occur).
-
-    - <dfn for="DeprecationReportBody">message</dfn>: A human-readable string
-      with details typically matching what would be displayed on the developer
-      console. The message is not guaranteed to be unique for a given
-      [=DeprecationReportBody/id=] (eg. it may contain additional context on how
-      the API was used).
-
-    - <dfn for="DeprecationReportBody">sourceFile</dfn>: If known, the file
-      which first used the indicated API, or null otherwise.
-
-    - <dfn for="DeprecationReportBody">lineNumber</dfn>: If known, the line
-      number in [=DeprecationReportBody/sourceFile=] where the indicated API
-      was first used, or null otherwise.
-
-    - <dfn for="DeprecationReportBody">columnNumber</dfn>: If known, the column
-      number in [=DeprecationReportBody/sourceFile=] where the indicated API
-      was first used, or null otherwise.
-
-  <div class="example">
-  <pre>
-  {
-    "type": "deprecation",
-    "age": 27,
-    "url": "https://example.com/",
-    "user_agent": "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0",
-    "body": {
-      "id": "websql",
-      "anticipatedRemoval": "2020-01-01",
-      "message": "WebSQL is deprecated and will be removed in Chrome 97 around January 2020",
-      "sourceFile": "https://example.com/index.js",
-      "lineNumber": 1234,
-      "columnNumber": 42
-    }
-  }
-  </pre>
-  </div>
-
-  Note: Deprecation reports are always delivered to the <a>endpoint group</a>
-  named <code>default</code>; there is currently no way to override this.  If
-  you want to receive other kinds of reports, but not deprecation reports, make
-  sure to use a different name for the endpoint group that you choose for those
-  reports.
-
-</section>
-
 <section>
   <h2 id="implementation">Implementation Considerations</h2>