-
Notifications
You must be signed in to change notification settings - Fork 36
Issues: w3c/reporting
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
process header
algorithm references undefined fetch response HTTPS state
#272
opened Oct 11, 2024 by
simonwuelker
Clarifying behavior when both Reporting-Endpoints and Report-To headers are provided?
#267
opened Dec 5, 2023 by
freyalaluna
Reports should be queued for reporting observers even when no endpoint exists
#265
opened Oct 12, 2023 by
clelland
Could there be a way to collect Crash/Intervention reports without collecting Depreciation reports?
#263
opened May 5, 2023 by
Sora2455
HPKP is deprecated and unshipped – should not be used as example
#247
opened Nov 2, 2021 by
johnwilander
Report delivery - executing steps "asynchronously" and queueing tasks on which event loop?
#235
opened Feb 25, 2021 by
zcorpan
Report Delivery
privacy-tracker
Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.
#194
opened Jan 13, 2020 by
annevk
Reporting API should be opt-in
privacy-tracker
Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.
#168
opened Jul 18, 2019 by
pes10k
Clarify behavior of duplicate endpoint URLs
network reporting
Issues relating specifically to the network reporting spec
#166
opened Jul 18, 2019 by
sburnett
Endpoint weighted selection algorithm fails if weights are 0
network reporting
Issues relating specifically to the network reporting spec
report-delivery
Covers the core delivery of reports via HTTP
#153
opened Apr 1, 2019 by
chlily1
Previous Next
ProTip!
Follow long discussions with comments:>50.