Minefield fell down hard Can't copy UserID Have to type so much
You can copy the user ID using the context menu, however most users probably don't know that and use the key command. Requesting blocking.
I really don't see why this is a big deal. Shaver was confused and thought he needed the UserID for something, but it's not actually useful.
(In reply to comment #2) > I really don't see why this is a big deal. Shaver was confused and thought he > needed the UserID for something, but it's not actually useful. Right. What would be useful is to be able to copy some information by which you could look up the report on crash-stats.mozilla.com, like the report ID, but that's not available in the dialog.
Because we don't have it until we actually submit the report, because it comes from the server.
It sucks that _anything_ we display can't be copied, and we should fix those cases.
Two things: 1. As a user, I should be able to find my reports. That's a Socorro bug, but being able to copy the user ID is a good first step. (I'll file the Socorro bug.) 2. Having text in a textbox that can be highlighted makes it seem like it can be copied. If the intention is to have it unhighlightable, let's change the field to something else. But as I said in #1, I'd like it to be selectable so a user can find their own crashes (once that gets added to Socorro).
By "find my reports" what do you mean? We obviously store the report IDs on the client, and nightly-tester-tools makes that available in the UI... If you mean "search in socorro with my email address", I believe that bug is already filed, but only people with LDAP accounts will be able to do that (for obvious privacy reasons), and we don't have an LDAP-authed admin section yet.
I mean "search in Socorro with my user ID".
What userid? You mean the automatically-generated GUID? That has the same privacy concerns...
No, it *doesn't* have the same concerns, because the automatically-generated GUID isn't personally-identifying information, like an email address is, until/unless it's otherwise correlated.
It is correlatable against other crash reports.
(In reply to comment #11) > It is correlatable against other crash reports. Plus, we show the URL for the last site the browser was on, so you could easily correlate what sites a user visits based on the UserID.
Yes, it can be used to correlate against other reports (and the URL is going away in public report displays, no?), but it doesn't have the *same* concerns as an email address, and it doesn't have ones that are as *bad*.
So this bug is about allowing that text to be copied. Since it's in a textbox, I see no reason why that should be disallowed. I'll file a new bug in Socorro (on code.google.com) about allowing users to search by user ID. I, like shaver, thought we were eventually going to remove that URL from the public view as well. Regardless, those sites and crashes are public as it is. The discussion from this bug will be in the Socorro issue I file later today.
No, the URL is not going away in public reports... we've always had it, and it's very helpful.
I don't see a URL in http://talkback-public.mozilla.org/search/start.jsp?search=2&type=iid&id=34610705 -- and I'm glad. It is nowhere _near_ clear enough from that dialog that if you leave that box checked you're going to publish the URL to the whole world.
Also note that there's no way currently to disable sending the URL along with a Breakpad report (bug 384207).
This has morphed into a more general discussion of our crash reporting. Perhaps we should take this to the newsgroups? We were using .quality in the past, but feel free to cross-post if you want to reach a wider audience. We should figure out some good balance of what helps us, helps users, and protects people's privacy.
This isn't very important, but maybe we'll fix it with some other changes we're picking up. Hopefully getting Socorro to email the user will make it more obvious where your reports are.
Severity: normal → trivial
oh hai, i fixed ur bugz. also you have about:crashes which is more awesomeness than your brain can handle anyway.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9beta3
You need to log in before you can comment on or make changes to this bug.