<div dir="ltr"><div dir="ltr">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?<div><br></div><div>Thanks!</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Dec 14, 2020 at 10:09 AM Ian Clelland <<a href="mailto:iclelland@chromium.org">iclelland@chromium.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi WebKit!<br><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>Thanks!</div><div>Ian</div><div><br></div><div>Some relevant links:<br></div><div>* Explainer: <a href="https://github.com/w3c/reporting" target="_blank">https://github.com/w3c/reporting</a><br>* Spec: <a href="https://w3c.github.io/reporting" target="_blank">https://w3c.github.io/reporting</a><br>* Recently-opened TAG review: <a href="https://github.com/w3ctag/design-reviews/issues/585" target="_blank">https://github.com/w3ctag/design-reviews/issues/585</a><br><br></div></div>
</blockquote></div></div>