w3c / w3c/reporting

Reports should be queued for reporting observers even when no endpoint exists

Open
#265 0 comments 0 reactions 1 assignee View on GitHub

@clelland is already working on this.

Since Oct 23, 2023.

Dominant language
Bikeshed
Stars
84
Forks
39
Avg merge
1d 20h
Merged PRs (30d)
1

Description

In some cases, it may be desirable to produce reports which can be seen by reporting observers, even when no endpoint has been configured.

Permissions-policy violations, for instance, can be observed and reacted to in the running page, but enabling this requires sending an endpoint value into generate and queue a report.

Callers could use a deliberately invalid name, so that the later processing steps will discard the queued report, but it would be better to make it optional in the first place.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.