Closed
Bug 384207
Opened 17 years ago
Closed 17 years ago
Crash Reporter client should include a URL field
Categories
(Toolkit :: Crash Reporting, defect, P1)
Toolkit
Crash Reporting
Tracking
()
VERIFIED
FIXED
mozilla1.9beta2
People
(Reporter: moco, Assigned: ted)
References
Details
(Keywords: privacy)
Attachments
(3 files, 3 obsolete files)
52.10 KB,
image/png
|
Details | |
23.49 KB,
patch
|
dcamp
:
review+
|
Details | Diff | Splinter Review |
4.39 KB,
patch
|
dcamp
:
review+
|
Details | Diff | Splinter Review |
add "url" and "comment" area to breakpad ui.
originally mentioned as a comment of bug #358082, but that bug is now fixed and also bug #366971 (marked a dup of bug #358082)
currently the breakpad ui asks for email address, per beltzner's mockup, but there is no text area enter my comments and the URL.
See also bug #375083 about "
Send URL of active tab to the crash report as metadata".
Assignee | ||
Comment 1•17 years ago
|
||
There's already bug 382538 on a comment field, I guess we don't have a bug on entering the URL.
Reporter | ||
Comment 2•17 years ago
|
||
morphing bug, per Ted's comment.
Summary: add "url" and "comment" area to breakpad ui → Crash Reporter client should include a URL field
Comment 3•17 years ago
|
||
I don't think we want a field for entering the URL... we should just record the latest URL if possible, and let any other information come in through the comments field.
Assignee | ||
Comment 4•17 years ago
|
||
We ought to at least display what we collected from the app, with a checkbox to let the user not send it.
Comment 5•17 years ago
|
||
I think we should display it in the details view. Why display it in the standard view, and why do we need a checkbox? If it's for privacy, I think that's a false sense of privacy, because the URL can end up in the minidump data quite easily.
Comment 6•17 years ago
|
||
I've come across another issue where the wrong url is sent.
Some crashes which happen during page load crash before |this._updateCrashReportURL(aWindow)| is called. This results in a crash report with the previous url from the tab in place of the url causing the crash. Example: bp-d49092eb-442b-11dc-8d02-001a4bd43ef6
The crashing url for this report is http://www.unl.edu/rhames/bonobo/bonobo.htm
I don't really understand what happened in bug 375083 but I gather that sessionStore isn't being triggered early enough during page load to update the current tab. I also see this sometimes with session store not saving a crashing tab (couldn't find a bug for that) but as that would lead to a cycle of crashes when restoring it doesn't seem desirable;e to fix.
I would like to have an editable URL field so I can submit the correct url for crash reports related to this kind of crash.
Comment 7•17 years ago
|
||
beltzner, what are your thoughts on this? The URL is displayed when you choose "View Data", but not everyone is going to look there. It seems rather sneaky to me to send the URL without telling the user.
Keywords: uiwanted
Comment 8•17 years ago
|
||
(In reply to comment #5)
> I think we should display it in the details view. Why display it in the
> standard view, and why do we need a checkbox? If it's for privacy, I think
> that's a false sense of privacy, because the URL can end up in the minidump
> data quite easily.
There's a difference between "can end up in the minidump" and "is always sent intentionally in it's own field [and displayed in the web interface for anyone to see]". The raw minidump data isn't available to the public and extracting the URL from it is presumably nontrivial.
Not giving the users a choice to opt-out of sending the URL sounds like the wrong thing to do, and could result in fewer submitted reports from people who are privacy conscious.
Updated•17 years ago
|
Updated•17 years ago
|
Flags: blocking1.9?
Assignee | ||
Updated•17 years ago
|
Assignee: nobody → ted.mielczarek
Assignee | ||
Comment 9•17 years ago
|
||
Ok, my plan for this is:
If the .extra data from the crashing app includes a "URL" field, display a textbox containing the URL (labelled URL), to allow the user to edit or delete it. This should make things work ok for Thunderbird et. al.
Updated•17 years ago
|
Flags: blocking1.9? → blocking1.9+
Updated•17 years ago
|
Priority: -- → P2
Assignee | ||
Updated•17 years ago
|
Target Milestone: --- → mozilla1.9 M10
Comment 11•17 years ago
|
||
Ted is this rollin?
Assignee | ||
Comment 12•17 years ago
|
||
It's in progress. Just a little slow cause I have to do it x 3 platforms.
Assignee | ||
Comment 13•17 years ago
|
||
Just gonna do each platform separately, since they're all different anyway. This patch does include the extra string in locales/ though. My cocoa skills are mostly copypasta, so let me know if I'm doing anything stupid here.
This patch adds a URL field with a checkbox above it for "Include this URL in the crash report". The box is checked by default, and the URL field is pre-filled with the URL from the extra data. If no URL was provided with the extra data, the checkbox and text field are hidden completely.
Screenshot: http://people.mozilla.com/~tmielczarek/crashreporter-url.png
FYI:
- int oldRestartWidth = restartFrame.size.width;
+ float oldRestartWidth = restartFrame.size.width;
That kills a compiler warning, apparently I was supposed to be using float there.
Attachment #289528 -
Flags: review?(dcamp)
Assignee | ||
Comment 14•17 years ago
|
||
Comment 15•17 years ago
|
||
Comment on attachment 289528 [details] [diff] [review]
mac support + added string
Changing the email field updates the checkbox and details field appropriately (see controlTextDidChange). The URL button should probably do the same thing.
Comment 16•17 years ago
|
||
This is gonna change a little as per bug 404855: we're going to have a checkbox (default on) which allows the user to exclude their URL, and they'll be able to see the URL itself if they choose to view the report data. That way we don't have to include a textbox, which makes the dialog a little larger.
(removing uiwanted)
Keywords: uiwanted
Assignee | ||
Updated•17 years ago
|
Attachment #289528 -
Attachment is obsolete: true
Attachment #289528 -
Flags: review?(dcamp)
Assignee | ||
Comment 17•17 years ago
|
||
So here's what I've got currently.
Assignee | ||
Comment 18•17 years ago
|
||
A few thoughts:
re: comment 6:
I'll file a different bug about trying to get the URL more accurately. We shouldn't make anyone type in a URL just because we aren't getting it right. We should be able to watch a different event for when navigation happens and grab the URL at the start.
re: comment 7:
I'm still not 100% happy with the fact that the URL still isn't visible with my latest changes, but the crash reporter UI is getting way overloaded. We need to keep it sane so it doesn't scare people. I think having the checkbox there is hopefully warning enough to people that we're including a URL.
Assignee | ||
Comment 19•17 years ago
|
||
Ok, this has the string changes + the OS X gui changes.
Attachment #290563 -
Flags: review?(dcamp)
Assignee | ||
Comment 20•17 years ago
|
||
Ok, combined osx+win patch.
Attachment #290225 -
Attachment is obsolete: true
Attachment #290563 -
Attachment is obsolete: true
Attachment #290593 -
Flags: review?(dcamp)
Attachment #290563 -
Flags: review?(dcamp)
Comment 21•17 years ago
|
||
Comment on attachment 290593 [details] [diff] [review]
osx + win patch [checked in]
> [viewReportScrollView retain];
> [viewReportScrollView removeFromSuperview];
>
>+ if (gQueryParameters.find("URL") != gQueryParameters.end()) {
>+ // save the URL value in case the
need to finish that thought :)
Attachment #290593 -
Flags: review?(dcamp) → review+
Assignee | ||
Comment 22•17 years ago
|
||
Comment on attachment 290593 [details] [diff] [review]
osx + win patch [checked in]
Checked this in, will get Linux as soon as I get back to a Linux build env.
Attachment #290593 -
Attachment description: osx + win patch → osx + win patch [checked in]
Assignee | ||
Comment 23•17 years ago
|
||
Turns out this was pretty easy for Linux!
Attachment #290631 -
Flags: review?(dcamp)
Updated•17 years ago
|
Attachment #290631 -
Flags: review?(dcamp) → review+
Assignee | ||
Comment 24•17 years ago
|
||
Checked the Linux bits in.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Comment 25•17 years ago
|
||
verified fixed with Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9b2) Gecko/2007121016 Firefox/3.0b2 and XP Version
- > Changing to verified
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•