Request Description
We need help to implement the crash-reporting UI. Here is a short description of the project:

The goal of the crash-reporting API is to share crash reports with websites. If a website is interested in crash-reports and the browser crashes when visiting that website, a report will be generated and sent to it.

This has a few privacy implications and it would be great if we ask the user to confirm that they want to send the crash-report. As you probably know, we already collect crash-reports on the mozilla servers and we already ask the user for confirmation before sending them. This confirmation dialog is called "crash reporter" and the UI is this one: about:tabcrashed

When a crash occurs, the browser knows if the crash has been triggered by a particular website. When we display the Crash-Report UI, we can add an extra checkbox (or something similar) to ask the user their permission to send the crash-report to the website.

The privacy concern is about sharing sensitive data with 3rd parties.

Deadline
August/September

Priority Level
2

Priority Level Description
This project is not high-priority at the moment, and we have a few missing parts to be implemented yet.

Do we have a decision about us as Firefox being ok with sharing potential sensitive data with 3rd parties?
This seems to be a policy question first, as even if users tick a checkbox we can not expect everyone understands the full implication of that action. Or is there something else we can do to strip the data of sensitive bits before sharing? To make it a safer choice to opt in?

Could you please also provide a screenshot of the UI in question for reference - ideally on Windows 10, or a way to trigger the UI. Thanks.

At this point we're not planning on sending highly sensitive data. https://wicg.github.io/crash-reporting/index.html#sample-reports has the data we would send. Which URL crashed and whether that was due to out-of-memory or unresponsiveness. In the future we might want to expand on this so I guess it's worth considering how things might evolve at that point.

about:tabcrashed shows the current UI (I think). A variant of that could be something like:

Gah. example.com just crashed.
[ ] Report this crash to example.com
[Close] [Restore]

and if you toggle the checkbox the buttons might say:

[Report and close] [Report and restore]

And perhaps we could remember the checkbox toggle for future crashes.

Another thing here is that we should only offer this for first-party (i.e., origin matches the address bar) crashes. We don't want to show the user domains of pages they haven't navigated to I think. Not entirely sure how we would offer that without Fission now I think of it.

Closing this as we will not get to it unless it is prioritized highly against one of our core focus areas (push, pull, revenue).
If you thin I made a mistake please reach out and let's align with the relevant PM.

Agreed it makes sense to not prioritize it right now, but I do think we want to tackle this eventually. I guess we can reopen this at that point or file a new bug that points to this one.