Intent to Prototype and Ship: ReportingObserver on workers

[Yutaka Hirano]

Contact emails

yhi...@chromium.org

Explainer

No explainer

Spec

https://w3c.github.io/reporting/ 

No tag review - this is a small extension and has already been in the spec.

Summary

ReportingObserver is an interface that allows web developers to observe reports made by user agents. In Chromium it is exposed only to Window, but I'd like to expose it to Worker as we'd like to observe COEP violations for fetches initiated in workers.

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

Yes.

Demo link

N/A

Debuggability

N/A

Risks

Interoperability and Compatibility

Describe the degree of interoperability and compatibility risk. For a new feature, the main risk is that it fails to become an interoperable part of the web platform if other browsers do not implement it. For a removal, please review our principles of web compatibility.

There is virtually no compatibility risk as this is purely a feature addition. This change is positive for interoperability, given it has already been specced, and Firefox's (behind-the-flag) implementation also exposes the interface to Worker.

Edge: No signals

Firefox: In development

Safari: No signals

Mozilla is developing ReportingObserver behind a flag. Their current implementation matches the spec, which means ReportingObserver is exposed to both Window and Worker.

Ergonomics

Are there any other platform APIs this feature will frequently be used in tandem with? 

Could the default usage of this API make it hard for Chrome to maintain good performance (i.e. synchronous return, must run on a certain thread, guaranteed return timing)?

The only reports available in workers are reports made by Cross-Origin-Embedder-Policy at this moment.

Activation

Will it be challenging for developers to take advantage of this feature immediately, as-is?

Would this feature benefit from having polyfills, significant documentation and outreach, and/or libraries built on top of it to make it easier to use?

There is an article describing how to use Cross-Origin-Embedder-Policy. That article doesn't cover ReportingObserver, but we may augment it.

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

https://wpt.fyi/results/reporting/idlharness.any.worker.html?label=experimental&label=master&aligned

Entry on the feature dashboard

This is a small extension so I think a new entry is not needed.

Requesting approval to ship?

Yes.

[Mounir Lamouri]

This looks great. I would recommend creating a new Chrome Status entry. Alternatively, you could merge this into the original entry for ReportingObserver (and use the opportunity to update it).

Otherwise, this seems a fairly straightforward benefit to the platform. Non-OWNER LGTM.

-- Mounir

--
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/CABihn6F%3DRZOYwQKgwhTe%3DHUXDrEk42W8rA85BeB3m%3D4vv%2BD%3DXw%40mail.gmail.com.

[TAMURA, Kent]

LGTM1.

This is a straight-forward change, and the Firefox status is a very good signal.

--

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/CABihn6F%3DRZOYwQKgwhTe%3DHUXDrEk42W8rA85BeB3m%3D4vv%2BD%3DXw%40mail.gmail.com.

--

TAMURA Kent
Software Engineer, Google

[Stephen Mcgruer]

> Entry on the feature dashboard

> This is a small extension so I think a new entry is not needed.

Will web developers not wish to know about this, if the goal is for them to use it in their workers? (since it requires activation based on your post). I would suggest a chromestatus entry to help communicate it to them!

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqHhTX3q_SGJvrBCR8dr-4nzQB1c%3Dfz7bpF9Jkama_c%2B6g%40mail.gmail.com.

[Yoav Weiss]

LGTM2

On Mon, Apr 20, 2020 at 5:24 AM Yutaka Hirano <yhi...@chromium.org> wrote:

Contact emails

yhi...@chromium.org

Explainer

No explainer

You could point to https://github.com/w3c/reporting/blob/master/EXPLAINER.md which is not worker specific, but would help folks understand what that feature is trying to solve.

--

[Mike West]

LGTM3.

-mike

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACj%3DBEgsjs4XLrX-vQo%2BAXbXuyBFNQgLDOd9VDzkPBJTHe0Eiw%40mail.gmail.com.

[Yutaka Hirano]

Thank you.

I created https://www.chromestatus.com/feature/6310316751192064.

[waynec...@gmail.com]