The toolbox-minimize feature was disabled in bug 1177463 because we didn't have a good idea about how the UI for this feature should look like and didn't want to ship the temporary UI to aurora. This bug should be used to re-enable this feature. Here's what it looked like: https://dl.dropboxusercontent.com/u/1212936/lice/toolbox-min-demo.gif
3 years ago
Depends on: 1177463
3 years ago
For the discussion about the minimize feature UI, see from bug 867838 comment 26 to bug 867838 comment 33. Also another screenshot of the feature: https://dl.dropboxusercontent.com/u/714210/toolbox-minimize.gif
We are close to a year now. Is this something we are going to do? I'm asking because I end up hiting this dead piece of code and wonder if we should really maintain it. Is it really worth rewriting disabled code from xul to html or dechromify it?!
Firebug has a minimize button. The idea behind the button is to let it run in the background, so e.g. network requests are tracked. Here are some ideas how the UI could look like: To toggle minimization: - Button within the DevTools toolbar (like before) - Double-clicking the DevTools toolbar (or their edge) - Browser toolbar button (like Firebug has it) - Keyboard shortcut (like F12 in Firebug) Minimized state: - Display only the DevTools toolbar (like before) - Display only an icon in the corner of the browser window - Display the browser toolbar button differently (like Firebug, where colored = minimized, grayscale = disabled) Sebastian
9 months ago
Severity: normal → enhancement
Priority: -- → P3
Heads up: In bug 1450624 I intend to remove the minimize feature.
Bug 1450624 has landed. Given the decision not to re-enable this feature, I'm resolving this as invalid.
Status: NEW → RESOLVED
Last Resolved: 5 months ago
Resolution: --- → INVALID
> Given the decision not to re-enable this feature, I'm resolving this as invalid. Can you give some of the rationale behind this decision to close? As far as I could see from bug 1450624, the code was removed because it was considered less maintenance to remove the out-of-date code and to re-implement it once the UI questions were resolved, than to keep the disabled code 'live'. There is nothing in that bug that indicates that this feature is not wanted. There is a strong use-case for being able to hide the debugger UI whilst still capturing events in the background, and if there is not currently any way of doing that there should be an open bug to cover re-adding that lost functionality.
(In reply to Mark Clements from comment #6) > > Given the decision not to re-enable this feature, I'm resolving this as invalid. > > Can you give some of the rationale behind this decision to close? I don't know of any plans to revisit the minimize feature but Patrick should make the call on this. Re-opening for now.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
(In reply to Mark Clements from comment #6) > There is a strong use-case for being able to hide the debugger UI whilst > still capturing events in the background, and if there is not currently any > way of doing that there should be an open bug to cover re-adding that lost > functionality. +100
You need to log in before you can comment on or make changes to this bug.