Closed Bug 815451 Opened 13 years ago Closed 8 years ago

Linkify "privacy policy" text in "What's in a crash report?" information page

Categories

(Firefox OS Graveyard :: Gaia::System, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: Margaret, Unassigned)

References

Details

This is a follow-up to bug 813128. I punted on including a link to our privacy policy in the crash reporter dialog because we'd have to figure out a flow for opening a link from a modal dialog. If we decide we that this link is important, we can fix it here. Otherwise, we can just close this bug. Here's what Larissa had to say in bug 813128 comment 14: The question is really about system vs app modal dialog behavior. What happens when the user hits the home button when a crash dialog comes up, for example. Do we allow the user to close the crash dialog, or do we disable the home button? (I vaguely remember discussing this with Josh, but I don't know if we ever came to a good conclusion.) In the same way, if we send the user out to the browser, is this the same as dismissing the crash report, or does the crash report persist on the home screen for the user to go back to? If we are being consistent with the definition of a system modal dialog, we wouldn't let the user exit without making a choice. Following this line of thought, the crash report screen would persist on the home screen even if the user taps the home button or goes to view our privacy policy on a webpage. The alternative is to say that the crash dialog gets dismissed (with some default choice) when the user hits the home button or the privacy policy link. I don't link this behavior because the user hasn't really made a choice, it was just sort of made for him. Does my first suggestion (persisting the crash report on the home screen) sound good to people / is it feasible without changing too much behavior?
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.