Chrome User Experience Report mention is confusing

[npm1]

It's not clear to me what the goal is here. Is this meant to be a web API, as specified by the link? If it is, and not meant to be a Chrome-specific tool, then I'm not sure 'Chrome User Experience Report' would be a feasible option.

[igneel64]

From reading the initial draft of this proposal and the section of exposing the abandonment and especially Option B (Reporting API), in my eyes it qualifies as a Web API in the sense that it could be queriable through a Reporting Observer. Also if the Reporting API option is technically feasible, concept-wise at least it won't be a Chrome-specific feature.

Might be overreaching from this point on
To be completely honest (or just really naive as I do not know yet the implementation specifics of CRUX), I think that using the Reporting API, we can have both Option A and B. By having Chrome as a user-agent sending opaquely (not queryable through observers) the user-abandonement Reporting entry to CRUX as if it was implemented by the main navigation document, it becomes possible to my mind.

[npm1]

Yea, I think doing both is feasible. Perhaps I misread 'options' as being one or the other. It can be in Chrome User Experience Report and be reported elsewhere as well.

[neilstuartcraig]

As I mentioned in #1, I'd very much like to see this being reported via the reporting API a la NEL. IMO, this would need to provide for sampling in the same way as NEL does. We'd probably be swamped from time to time if we reported on 100% of abandons.