From c6ec0983ef7a4f24589801d1f6017203ae0abbdc Mon Sep 17 00:00:00 2001 From: YFdyh000 Date: Thu, 2 Nov 2017 21:16:35 +0800 Subject: [PATCH] fix a typo for csp reporting --- Dashboard:-Settings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Dashboard:-Settings.md b/Dashboard:-Settings.md index 76a6eb3..409ef05 100644 --- a/Dashboard:-Settings.md +++ b/Dashboard:-Settings.md @@ -88,7 +88,7 @@ Consider this excerpt from [Reporting API / Privacy Considerations](http://wicg. > > That said, it can’t be the case that this general benefit be allowed to take priority over the ability of a user to individually opt-out of such a system. Sending reports costs bandwidth, and potentially could reveal some small amount of additional information above and beyond what a website can obtain in-band ([NETWORK-ERROR-LOGGING], for instance). **User agents MUST allow users to disable reporting with some reasonable amount of granularity in order to maintain the priority of constituencies espoused in [HTML-DESIGN-PRINCIPLES].** -There is currently no way to easily toggle CSP reporting in either Chromium of Firefox. This per-site switch is to address this shortcoming. +There is currently no way to easily toggle CSP reporting in either Chromium or Firefox. This per-site switch is to address this shortcoming. Note that as opposed to all other network requests, behind-the-scene network requests which are actual CSP reports will also be filtered out according to this setting. So if you globally disable CSP reporting in uBO, this will also apply to behind-the-scene network requests.