Open
Bug 1242055
Opened 9 years ago
Updated 3 years ago
Change "Record Allocation stacks" to an icon
Categories
(DevTools :: Memory, defect, P2)
DevTools
Memory
Tracking
(Not tracked)
NEW
People
(Reporter: ntim, Unassigned)
Details
(Whiteboard: [devtools-ux])
Attachments
(2 files)
The checkbox currently looks odd, especially the label that looks concatenated with "View:".
| Reporter | ||
Comment 1•9 years ago
|
||
| Reporter | ||
Comment 2•9 years ago
|
||
| Reporter | ||
Updated•9 years ago
|
Whiteboard: [devtools-ux]
Comment 3•9 years ago
|
||
Tim, I know there was some discussion on IRC about this and why it made sense. Can you recap it here for me?
Updated•9 years ago
|
Flags: needinfo?(ntim.bugs)
| Reporter | ||
Comment 4•9 years ago
|
||
(In reply to Helen V. Holmes (:helenvholmes) (:✨) from comment #3)
> Tim, I know there was some discussion on IRC about this and why it made
> sense. Can you recap it here for me?
This idea was brought up to fix a current esthetic issue (how the checkboxes are oddly placed). Then we thought an icon was better for these reasons:
- the "Invert tree" checkbox is context aware (and disappears in some situations), the "Record Allocation Stacks" checkbox doesn't follow that pattern.
- The "Record Allocation Stacks" only affects future recordings, not the current one
Start of the conversation: http://logs.glob.uno/?c=mozilla%23devtools&s=22+Jan+2016&e=22+Jan+2016#c153120
Where it gets interesting: http://logs.glob.uno/?c=mozilla%23devtools&s=22+Jan+2016&e=22+Jan+2016#c153214
Flags: needinfo?(ntim.bugs)
Comment 5•9 years ago
|
||
Was it not originally made into a checkbox because it was an option when recording?
| Reporter | ||
Comment 6•9 years ago
|
||
(In reply to Helen V. Holmes (:helenvholmes) (:✨) from comment #5)
> Was it not originally made into a checkbox because it was an option when
> recording?
Yes.
Updated•9 years ago
|
Has STR: --- → irrelevant
Priority: -- → P2
Updated•7 years ago
|
Product: Firefox → DevTools
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•