Intent to Ship: Intervention Reports

[paul...@chromium.org]

Contact emails

paul...@example.com, rby...@example.com

Explainer

https://github.com/w3c/reporting/blob/master/EXPLAINER.md#interventions

Spec

https://w3c.github.io/reporting/#intervention-report  

Tag Review

https://github.com/w3ctag/design-reviews/issues/195

Summary

Intervention reports are a new type of report to be observed by ReportingObserver and to be routed to the Reporting API backend. Intervention reports indicate that a user agent has decided not to honor a request made by the application (e.g. for security, performance or user annoyance reasons).

Link to “Intent to Implement” blink-dev discussion

https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/83uwiEBHMGc

Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

Yes.

Risks

No change in risks beyond that of ReportingObserver.

Is this feature fully tested by web-platform-tests? Link to test suite results from wpt.fyi.

This feature is tested as part of ReportingObserver, which is currently in the process of having new testing infrastructure implemented. Currently, these features are not testable via web-platform-tests, but will be once the WebDriver Extension function outlined here is implemented.

Entry on the feature dashboard

https://www.chromestatus.com/features/5544632075157504

[Joe Medley]

Paul,

Do you have a tracking bug I can star?

Joe

Joe Medley | Technical Writer, Chrome DevRel | jme...@google.com | 816-678-7195

If an API's not documented it doesn't exist.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/bfe426a9-463a-41de-8956-2133a4e18db8%40chromium.org.

[paul...@chromium.org]

Correction on the contact emails:

paul...@chromium.org, rby...@chromium.org 

[paul...@chromium.org]

There isn't really an explicit tracking bug on intervention reports right now, but this bug has been used for work done on intervention reports so far:

https://bugs.chromium.org/p/chromium/issues/detail?id=564071

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

[Chris Harrelson]

LGTM1

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/bfe426a9-463a-41de-8956-2133a4e18db8%40chromium.org.

--

You received this message because you are subscribed to the Google Groups "blink-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/06127822-268e-4be1-8e43-f3776a439acf%40chromium.org.

[Mike West]

LGTM2. This will help developers understand the ways in which the browser is interacting with their code, and will hopefully lead to more rapid action against the kinds of behaviors Blink tends to intervene against.

-mike

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw-J2Wrbf1LnHQDErDH%3DkUZs378fWyTXnuNjuWkj8U6M-A%40mail.gmail.com.

[Yoav Weiss]

LGTM3

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKXHy%3De4eh%2B9v6ThOqO025JjUqWb%2BZn%2BVERX%3Dj2oPrRkLh7C2A%40mail.gmail.com.