Closed
Bug 1451901
Opened 6 years ago
Closed 4 years ago
Is there a way to collapse all about:memory subtrees at once, or open about:memory fully collapsed?
Categories
(Developer Documentation Graveyard :: Developer Tools, enhancement, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: loren, Unassigned)
References
()
Details
:: Developer Documentation Request Request Type: New Documentation Gecko Version: 59 Branch Technical Contact: :: Details I've been struggling with this for awhile, I find the full about:memory tree (1441 lines in my current example) truly overwhelming. I know about this: "Sub-trees can be collapsed or expanded by clicking on them. If you find any particular tree overwhelming, it can be helpful to collapse all the sub-trees immediately below the root, and then gradually expand the sub-trees of interest." In my current example, "Explicit Allocations" collapsed nicely, but the first "Other Measurements" below it took 16 clicks before I could see the next heading. To collapse the whole display down to headings where I could spot the sections using a GB by themselves would take hundreds of clicks. Have I missed some quick trick to "collapse all" or open collapsed? Do people who use this daily use some other app to provide such capability? I have no idea if this is a feature request, or a documentation request, or just an admission of ignorance, but I've searched here and the web and the answer clearly is not obvious. Clues would be appreciated!
Updated•6 years ago
|
Component: General → Developer Tools
Priority: -- → P3
Reporter | ||
Comment 1•6 years ago
|
||
So if the solution is "New Documentation", does that mean there _is_ a way to "collapse all"? Could you please share it here? Or point me to it?
Comment 2•4 years ago
|
||
MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•