As of Firefox 149, we intend to turn on the Reporting API by default. *Summary:* The Reporting API provides a generic reporting mechanism for web applications to use to make reports available based on various platform features (for example Content Security Policy, Permissions-Policy, or feature deprecation reports) in a consistent manner.
Reporting API has two features, one where the report gets delivered to a ReportingObserver in JS code and one where the report get serialized and sent to a remote server. *Bugs:* Meta bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1631237 Ship bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1976074 *Specification:* https://w3c.github.io/reporting/ *Documentation:* https://developer.mozilla.org/en-US/docs/Web/API/Reporting_API *Standards Body:* W3C *Platform coverage:* all *Preference:* - dom.reporting.enabled - dom.reporting.header.enabled Both will be enabled by ship bug *DevTools bug:* N/A *Extensions bug:* N/A *Link to standards-positions discussion:* https://github.com/mozilla/standards-positions/issues/104 *Other browsers*: - Blink. shipping - Webkit, shipping *web-platform-tests*: Reporting API is tested in different suites: https://wpt.fyi/results/reporting https://wpt.fyi/results/content-security-policy/reporting-api https://wpt.fyi/results/feature-policy/reporting Feel free to reach out to me on matrix or slack for questions (preferable matrix), username sfarre Simon Farre -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAL%3DG%2Be0fgHhJVa16_gq9ZfmGW0w0SCUSwnwv2Jynmk3bNXPi7g%40mail.gmail.com.
