Closed
Bug 530186
Opened 16 years ago
Closed 16 years ago
Try to coerce about:crashes to display the report id with "bp-" already included
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: alqahira, Assigned: alqahira)
References
()
Details
(Whiteboard: [camino-2.0.1])
Attachments
(1 file)
|
1.29 KB,
patch
|
stuart.morgan+bugzilla
:
superreview+
|
Details | Diff | Splinter Review |
Continually explaining "prepend 'bp-' to the ID before you paste it into a bug" is getting really old, and is more confusing than necessary.
We should see if we can coerce about:crashes to just change the text inside the link (not the link itself) to include the "bp-" automatically, making it easier for users to copy and paste in a bug (or in the search field on crash-stats, which can now handle matching report IDs that include the bp- prefix).
Flags: camino2.0.2?
| Assignee | ||
Comment 1•16 years ago
|
||
This took all of, uh, 30 seconds :P
Attachment #413843 -
Flags: superreview?(stuart.morgan+bugzilla)
| Assignee | ||
Updated•16 years ago
|
Flags: camino2.0.1?
Comment 2•16 years ago
|
||
Comment on attachment 413843 [details] [diff] [review]
auto-prefixes the text
I'm not clear on why we want the bp-, but I presume there's a good reason ;) sr=smorgan.
Attachment #413843 -
Flags: superreview?(stuart.morgan+bugzilla) → superreview+
| Assignee | ||
Comment 3•16 years ago
|
||
So when we ask users to copy the crash ID from about:crashes and paste it in a bug, we don't have to explain adding "bp-" to the front of the id (for Bugzilla linkification).
It's easier for everyone to understand and do, and easier for us to explain; they can just copy/paste exactly what they see on about:crashes, and I can save about 3 lines on the Bugzilla FAQ ;)
Status: NEW → RESOLVED
Closed: 16 years ago
Flags: camino2.0.2?
Flags: camino2.0.1?
Flags: camino2.0.1+
Resolution: --- → FIXED
Whiteboard: [camino-2.0.1]
Comment 4•16 years ago
|
||
(In reply to comment #3)
> (for Bugzilla linkification).
Ah, that was the part I was missing; thanks :)
You need to log in
before you can comment on or make changes to this bug.
Description
•