Search results

CSS Error Source Element

Status: Open.

#278 In w3c/reporting;

· jabcreations opened on Feb 17, 2025

Is failure reporting a privacy leak?

Status: Open.

#276 In w3c/reporting;

· annevk opened on Jan 7, 2025

[reporting-1] Wrong Web IDL type for URLs in Reporting API

Status: Open.

#275 In w3c/reporting;

· dontcallmedom-bot opened on Jan 6, 2025

Accessibility Reports?

enhancement

Status: Open.

#274 In w3c/reporting;

· aluhrs13 opened on Dec 4, 2024

Generate Test Report: cannot check if something is a JSON object

Status: Open.

#273 In w3c/reporting;

· annevk opened on Nov 22, 2024

<code>process header</code> algorithm references undefined fetch response HTTPS state

Status: Open.

#272 In w3c/reporting;

· simonwuelker opened on Oct 11, 2024

Clarifying behavior when both Reporting-Endpoints and Report-To headers are provided?

Status: Open.

#267 In w3c/reporting;

· freyalaluna opened on Dec 5, 2023

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

Status: Open.

#265 In w3c/reporting;

· clelland opened on Oct 12, 2023

Could there be a way to collect Crash/Intervention reports without collecting Depreciation reports?

Status: Open.

#263 In w3c/reporting;

· Sora2455 opened on May 5, 2023

Broken references in Reporting API

Status: Open.

#261 In w3c/reporting;

· dontcallmedom-bot opened on Jan 27, 2023

Clarification on Retry mechanisms

Status: Open.

#260 In w3c/reporting;

· nicjansma opened on Jan 13, 2023

Allow for custom reports to be generated &amp; queued

Status: Open.

#259 In w3c/reporting;

· scottpledger opened on Jan 10, 2023