Closed
Bug 980529
Opened 11 years ago
Closed 7 years ago
Bottom-left buttons should be visible on call stack tab as well
Categories
(DevTools :: Debugger, defect)
DevTools
Debugger
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jryans, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [polish-backlog][difficulty=easy])
When the left-hand Source / Call Stack panel is switched to Call Stack, you lose access to the 3 buttons on the bottom: * Toggle blackboxing * Toggle pretty print * Toggle all breakpoints These still make sense to use when on the Call Stack panel, but currently they disappear.
Comment 1•11 years ago
|
||
The idea was that these buttons are applicable to sources, not individual frames. One could make the case that the action would still correspond to the source that "contains" the selected frame, but it may be confusing, too. CCing Darrin for consultation.
Reporter | ||
Comment 2•11 years ago
|
||
I follow the argument that blackboxing and pretty printing are about manipulating particular sources. But "toggle all breakpoints" is not tied to a particular source. At the very least, it would be good to keep "toggle all breakpoints" accessible no matter what tab you are on.
Comment 3•11 years ago
|
||
It's true that "toggle all breakpoints" doesn't fit well in that conceptual model, but IIRC the thinking was that it would be ugly to have a toolbar with only one button and we couldn't find a better place for it. Bug 815280 has the details. This is not a black-and-white case of course, so perhaps we could revisit this. Maybe we should add the pause-on-exceptions button from bug 882790 there, to make a proper toolbar.
Updated•10 years ago
|
Summary: Bottom-left buttons should be visible on call stack tab → Bottom-left buttons should be visible on call stack tab as well
Updated•10 years ago
|
Blocks: dbg-frontend
Updated•9 years ago
|
Whiteboard: [polish-backlog][difficulty=easy]
Comment 4•7 years ago
|
||
The new debugger doesn't have separate tabs here, so closing.
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•