Request for position on Reporting API (now with structured headers!)
Hi WebKit! In Chrome-land, we've been working on updating our implementation of the Reporting API to align with the spec changes made over the last year or so, which resolve a number of privacy issues, separating reports generated within the context of a single document from those which relate to overall network conditions, and isolating reports from unrelated documents. This also includes a new header, Reporting-Endpoints, whose value is not persisted between document loads. We're hoping to ship these updates sometime early in the new year, and would love to get the thoughts / opinions / feedback from WebKit developers. Thanks! Ian Some relevant links: * Explainer: https://github.com/w3c/reporting * Spec: https://w3c.github.io/reporting * Recently-opened TAG review: https://github.com/w3ctag/design-reviews/issues/585
Hi WebKit -- I sent this request out some time ago, but we're getting closer to shipping, and I'm wondering if there's a position I can refer to on the updated Reporting API? Thanks! On Mon, Dec 14, 2020 at 10:09 AM Ian Clelland <iclelland@chromium.org> wrote:
Hi WebKit!
In Chrome-land, we've been working on updating our implementation of the Reporting API to align with the spec changes made over the last year or so, which resolve a number of privacy issues, separating reports generated within the context of a single document from those which relate to overall network conditions, and isolating reports from unrelated documents. This also includes a new header, Reporting-Endpoints, whose value is not persisted between document loads.
We're hoping to ship these updates sometime early in the new year, and would love to get the thoughts / opinions / feedback from WebKit developers.
Thanks! Ian
Some relevant links: * Explainer: https://github.com/w3c/reporting * Spec: https://w3c.github.io/reporting * Recently-opened TAG review: https://github.com/w3ctag/design-reviews/issues/585
participants (1)
-
Ian Clelland