This may end up in the purview of Cloud Services. I envision a form similar to https://www.google.com/safebrowsing/report_phish/
After discussion with Bill, this should be hosted by us with the initial purpose of accepting feedback in an organized fashion.
Duplicate of this bug: 1083105
Points: --- → 3
(In reply to [:mmc] Monica Chew (please use needinfo) from comment #1) > After discussion with Bill, this should be hosted by us with the initial > purpose of accepting feedback in an organized fashion. Hi Monica/Javaun Can you help us understand the common use case for this kind of feedback? When do we want/expect users to report back to us and what would they be reporting? What kind of breakage are we expecting to hear about?
The point of this feedback is to vet the blocklist and make sure we aren't breaking high-volume sites for lots of users, and also helps us make decisions about what kind of allowlisting we need to support in the future. The current allowlist just disables tracking protection on the entire site, but power users may want more or different options. I chatted about this with psackl a while back and we came to the conclusion that it would be better to bundle reporting with "Disable protection for this site", since that's the clearest indication we have that users are dissatisfied. This would work similar to SSL reporting where the user can opt-in to sending the error (in our case, we'd need the top-level URL in addition to resources being blocked) just once or every time they click "Disable protection".
Created attachment 8553938 [details] Screen Shot 2015-01-23 at 1.06.29 PM.png Here's the SSL reporting form.
Monica says it very well. In addition to improving our tool, simply offering users this contextual option is a better experience, as it demonstrates Mozilla can easily accept their feedback.
Component: DOM: Security → Safe Browsing
Product: Core → Toolkit
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1240064
You need to log in before you can comment on or make changes to this bug.