w3c/reporting issues and pull requests

#186 - Disallow credentials from cross-origin reports

Pull Request - State: closed - Opened by clelland over 5 years ago - 5 comments

#180 - Update for recent WebIDL changes

Pull Request - State: closed - Opened by clelland over 5 years ago - 1 comment

#180 - Update for recent WebIDL changes

Pull Request - State: closed - Opened by clelland over 5 years ago - 1 comment

#179 - editorial: use new IDL constructor syntax

Pull Request - State: closed - Opened by marcoscaceres over 5 years ago - 1 comment

#179 - editorial: use new IDL constructor syntax

Pull Request - State: closed - Opened by marcoscaceres over 5 years ago - 1 comment

#178 - Define a max size for storage

Issue - State: open - Opened by hawkinsw over 5 years ago - 5 comments

#178 - Define a max size for storage

Issue - State: open - Opened by hawkinsw over 5 years ago - 5 comments

#176 - Report calls to console-methods like "console.error"

Issue - State: closed - Opened by nuxodin over 5 years ago - 1 comment

#170 - Remove include_subdomains flag and associated machinery

Pull Request - State: closed - Opened by clelland over 5 years ago - 3 comments

#170 - Remove include_subdomains flag and associated machinery

Pull Request - State: closed - Opened by clelland over 5 years ago - 3 comments

#169 - Privacy concerns regarding Reporting API

Issue - State: closed - Opened by pes10k over 5 years ago - 46 comments
Labels: privacy-tracker

#169 - Privacy concerns regarding Reporting API

Issue - State: closed - Opened by pes10k over 5 years ago - 46 comments
Labels: privacy-tracker

#168 - Reporting API should be opt-in

Issue - State: open - Opened by pes10k over 5 years ago - 16 comments
Labels: privacy-tracker

#167 - Remove "nel" example from standard text

Issue - State: closed - Opened by pes10k over 5 years ago - 3 comments
Labels: privacy-tracker

#167 - Remove "nel" example from standard text

Issue - State: closed - Opened by pes10k over 5 years ago - 3 comments
Labels: privacy-tracker

#166 - Clarify behavior of duplicate endpoint URLs

Issue - State: open - Opened by sburnett over 5 years ago - 2 comments
Labels: network reporting

#166 - Clarify behavior of duplicate endpoint URLs

Issue - State: open - Opened by sburnett over 5 years ago - 2 comments
Labels: network reporting

#163 - Clean up subdomain match logic

Pull Request - State: closed - Opened by dcreager over 5 years ago - 1 comment

#163 - Clean up subdomain match logic

Pull Request - State: closed - Opened by dcreager over 5 years ago - 1 comment

#162 - Add note about capability URLs

Pull Request - State: open - Opened by dcreager over 5 years ago - 2 comments

#162 - Add note about capability URLs

Pull Request - State: open - Opened by dcreager over 5 years ago - 2 comments

#161 - Consider credential-less reporting

Issue - State: closed - Opened by johnwilander over 5 years ago - 5 comments
Labels: report-delivery

#161 - Consider credential-less reporting

Issue - State: closed - Opened by johnwilander over 5 years ago - 5 comments
Labels: report-delivery

#160 - Are include_subdomains configurations allowed for raw IPs?

Issue - State: closed - Opened by chlily1 over 5 years ago - 2 comments
Labels: report-delivery

#160 - Are include_subdomains configurations allowed for raw IPs?

Issue - State: closed - Opened by chlily1 over 5 years ago - 2 comments
Labels: report-delivery

#159 - Disallow include_subdomains from eTLDs

Issue - State: closed - Opened by chlily1 over 5 years ago - 18 comments
Labels: report-delivery

#159 - Disallow include_subdomains from eTLDs

Issue - State: closed - Opened by chlily1 over 5 years ago - 18 comments
Labels: report-delivery

#157 - reporting cache replace operation not defined

Issue - State: closed - Opened by annevk almost 6 years ago

#156 - superdomain match for origin is bogus

Issue - State: closed - Opened by annevk almost 6 years ago
Labels: report-delivery

#156 - superdomain match for origin is bogus

Issue - State: closed - Opened by annevk almost 6 years ago
Labels: report-delivery

#155 - Capability URL problem bigger than advertized

Issue - State: closed - Opened by annevk almost 6 years ago - 3 comments
Labels: report-delivery

#155 - Capability URL problem bigger than advertized

Issue - State: closed - Opened by annevk almost 6 years ago - 3 comments
Labels: report-delivery

#153 - Endpoint weighted selection algorithm fails if weights are 0

Issue - State: open - Opened by chlily1 almost 6 years ago - 7 comments
Labels: report-delivery, network reporting

#153 - Endpoint weighted selection algorithm fails if weights are 0

Issue - State: open - Opened by chlily1 almost 6 years ago - 7 comments
Labels: report-delivery, network reporting

#147 - Relative URLs in endpoints configuration.

Issue - State: closed - Opened by koto about 6 years ago - 15 comments
Labels: report-delivery

#142 - Limit report delivery per page

Pull Request - State: open - Opened by paulmeyer90 about 6 years ago - 10 comments

#142 - Limit report delivery per page

Pull Request - State: open - Opened by paulmeyer90 about 6 years ago - 10 comments

#141 - Please add parsing tests for Report-To

Issue - State: open - Opened by annevk about 6 years ago - 2 comments

#141 - Please add parsing tests for Report-To

Issue - State: open - Opened by annevk about 6 years ago - 2 comments

#138 - What happens if "Let total weight be the sum of the weight value of each endpoint in endpoints" overflows

Issue - State: open - Opened by smaug---- about 6 years ago - 1 comment
Labels: network reporting

#138 - What happens if "Let total weight be the sum of the weight value of each endpoint in endpoints" overflows

Issue - State: open - Opened by smaug---- about 6 years ago - 1 comment
Labels: network reporting

#133 - endpoints should be stateless

Issue - State: closed - Opened by bakulf over 6 years ago - 4 comments

#133 - endpoints should be stateless

Issue - State: closed - Opened by bakulf over 6 years ago - 4 comments

#123 - Allow servers to specify a maximum report age?

Issue - State: open - Opened by dcreager over 6 years ago
Labels: enhancement, report-delivery

#123 - Allow servers to specify a maximum report age?

Issue - State: open - Opened by dcreager over 6 years ago
Labels: enhancement, report-delivery

#119 - Add "javascript error" report type?

Issue - State: closed - Opened by paulmeyer90 over 6 years ago - 12 comments

#119 - Add "javascript error" report type?

Issue - State: closed - Opened by paulmeyer90 over 6 years ago - 12 comments

#118 - Add "performance warning" report type?

Issue - State: closed - Opened by RByers over 6 years ago - 6 comments

#85 - Add note about custom metadata and spam prevention

Pull Request - State: open - Opened by dcreager over 6 years ago

#85 - Add note about custom metadata and spam prevention

Pull Request - State: open - Opened by dcreager over 6 years ago

#68 - Spam avoidance mechanism

Issue - State: open - Opened by dcreager about 7 years ago - 7 comments
Labels: report-delivery

#68 - Spam avoidance mechanism

Issue - State: open - Opened by dcreager about 7 years ago - 7 comments
Labels: report-delivery

#58 - Use low priority task queue and add takeRecords to ReportingObserver?

Issue - State: closed - Opened by RByers over 7 years ago - 5 comments
Labels: ReportingObserver

#58 - Use low priority task queue and add takeRecords to ReportingObserver?

Issue - State: closed - Opened by RByers over 7 years ago - 5 comments
Labels: ReportingObserver

#54 - Friendly TAG Review: relation to lifecycle events

Issue - State: closed - Opened by travisleithead over 7 years ago - 3 comments

#54 - Friendly TAG Review: relation to lifecycle events

Issue - State: closed - Opened by travisleithead over 7 years ago - 3 comments

#50 - Friendly TAG Review: service worker integration

Issue - State: closed - Opened by travisleithead over 7 years ago - 11 comments
Labels: ReportingObserver

#50 - Friendly TAG Review: service worker integration

Issue - State: closed - Opened by travisleithead over 7 years ago - 11 comments
Labels: ReportingObserver

#49 - reporting of metadata such as browser engine+version or other metadata chosen by page?

Issue - State: closed - Opened by dbaron over 7 years ago - 3 comments

#49 - reporting of metadata such as browser engine+version or other metadata chosen by page?

Issue - State: closed - Opened by dbaron over 7 years ago - 3 comments

#38 - remove garbage collection. fixes #23

Pull Request - State: closed - Opened by patrickkettner about 8 years ago - 1 comment

#38 - remove garbage collection. fixes #23

Pull Request - State: closed - Opened by patrickkettner about 8 years ago - 1 comment

#37 - update max-age section of explainer

Pull Request - State: closed - Opened by patrickkettner about 8 years ago - 2 comments

#37 - update max-age section of explainer

Pull Request - State: closed - Opened by patrickkettner about 8 years ago - 2 comments

#23 - GCing an active but failing endpoint is counterproductive

Issue - State: closed - Opened by juliatuttle over 8 years ago - 4 comments
Labels: report-delivery

#23 - GCing an active but failing endpoint is counterproductive

Issue - State: closed - Opened by juliatuttle over 8 years ago - 4 comments
Labels: report-delivery

#14 - Specify better data structures

Issue - State: closed - Opened by juliatuttle over 8 years ago - 1 comment
Labels: report-delivery

#14 - Specify better data structures

Issue - State: closed - Opened by juliatuttle over 8 years ago - 1 comment
Labels: report-delivery

#12 - Clarify input to HTTP-JFV in "Parse reporting endpoint tuples from _value_"

Issue - State: closed - Opened by juliatuttle over 8 years ago - 2 comments
Labels: report-delivery

#12 - Clarify input to HTTP-JFV in "Parse reporting endpoint tuples from _value_"

Issue - State: closed - Opened by juliatuttle over 8 years ago - 2 comments
Labels: report-delivery

#11 - Clarify behavior around "send reports" with active delivery attempts

Issue - State: open - Opened by juliatuttle over 8 years ago - 2 comments
Labels: report-delivery, network reporting

#11 - Clarify behavior around "send reports" with active delivery attempts

Issue - State: open - Opened by juliatuttle over 8 years ago - 2 comments
Labels: report-delivery, network reporting

#9 - `age` could become negative

Issue - State: open - Opened by estark37 almost 9 years ago - 1 comment
Labels: report-delivery, network reporting

#9 - `age` could become negative

Issue - State: open - Opened by estark37 almost 9 years ago - 1 comment
Labels: report-delivery, network reporting

#8 - Conflicting advice about switching networks

Issue - State: open - Opened by estark37 almost 9 years ago - 1 comment
Labels: report-delivery, privacy-tracker

#7 - Allow features to specify the criteria for considering a report successfully sent

Issue - State: open - Opened by estark37 almost 9 years ago - 1 comment
Labels: enhancement, report-delivery

#7 - Allow features to specify the criteria for considering a report successfully sent

Issue - State: open - Opened by estark37 almost 9 years ago - 1 comment
Labels: enhancement, report-delivery

#6 - Allow features to de-duplicate reports rather than sending redundant information

Issue - State: open - Opened by estark37 almost 9 years ago - 1 comment
Labels: report-delivery

#5 - Handle loops of reports

Issue - State: open - Opened by estark37 almost 9 years ago
Labels: report-delivery

#4 - Tie retries to user browsing behavior for better privacy?

Issue - State: open - Opened by estark37 almost 9 years ago - 8 comments
Labels: privacy-tracker

GitHub / w3c/reporting issues and pull requests