Closed
Bug 684339
Opened 13 years ago
Closed 13 years ago
about:memory should link to about:support
Categories
(Toolkit :: about:memory, defect)
Toolkit
about:memory
Tracking
()
RESOLVED
FIXED
mozilla9
People
(Reporter: ehsan.akhgari, Assigned: ehsan.akhgari)
Details
(Whiteboard: [MemShrink:P3])
Attachments
(1 file)
1.17 KB,
patch
|
n.nethercote
:
review+
|
Details | Diff | Splinter Review |
This information is usually very valuable when filing memory bugs. We should just add it to about:memory IMO.
Comment 1•13 years ago
|
||
Standard operating procedure should be including about:memory *and* about:support. But seeing as it's not, maybe ehsan is right.
Updated•13 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: [MemShrink]
Assignee | ||
Updated•13 years ago
|
Summary: about:memory should include the list of installed and active add-ons → about:memory should link to about:support
Whiteboard: [MemShrink] → [MemShrink:P3]
Assignee | ||
Comment 2•13 years ago
|
||
Comment 3•13 years ago
|
||
Comment on attachment 558581 [details] [diff] [review] Patch (v1) Review of attachment 558581 [details] [diff] [review]: ----------------------------------------------------------------- ::: toolkit/components/aboutmemory/content/aboutMemory.js @@ +259,5 @@ > : "<span class='option'><a href='about:memory?verbose'>More verbose</a></span>"; > text += "</div>"; > > text += "<div>" + > + "<span class='option'><a href='about:support'>Useful troubleshooting infromation</a></span>" + Drop the "Useful", and spell "information" correctly :) Then it'll just be "Troubleshooting information" which matches the menu item.
Attachment #558581 -
Flags: review?(nnethercote) → review+
Assignee | ||
Comment 4•13 years ago
|
||
Come on, "information" is sooooo 1990! :P http://hg.mozilla.org/integration/mozilla-inbound/rev/fd50c3e8aad3
Target Milestone: --- → mozilla9
Assignee | ||
Comment 5•13 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/fd50c3e8aad3
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•