w3c / w3c/reporting

Handle loops of reports

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

@clelland is already working on this.

Since Aug 15, 2022.

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

Description

For some reporting features, it's possible that sending a report could trigger another report that needs to be sent... which could trigger another, and so on, possibly infinitely. It would be nice for the spec to have concrete guidance on how UAs should detect and handle this situation.

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.