cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
ldetomi
New member
Status: New idea

I actually work with 2 FHD monitors of 27" and it is very useful to have browser on a screen and DevTools on the other one, but an entire 27" for each DevTools pane is almost too much, so… I sincerely would like to optimizie visualization having the possibility to split and undock panes, place them side-by-side.

Imagine that DevTools is maximized to entire screen and it is divided into 4 regions and in each one would be shown a different pane, for example we could contemporary see Inspector, Console, Debugger and Style Editor.

It would be a very “killer feature”


This is current implementation (second display is empty, but it could contain the entire Developer Tools but seeing only the same panes actually present on the bottom of the page)
Undock-Firefox-Developer-Tools-Current.jpg

This is a *super-quick* mockup of a splitted interface in which is possible to see in the same time, html inspector and debugger.

Going further, on sufficient big screens could be possible to use Windows aero-peek feature to have 4-panes at each corner of the second display, seeing contemporary, Html inspector, Debugger, CSS pane and Network, and so on...

Undock-Firefox-Developer-Tools-Html&Debugger.jpg

6 Comments
Status changed to: New idea
Jon
Community Manager
Community Manager

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.

Honza
Employee
Employee

I love the idea, thank you!

I filed a report here: https://bugzilla.mozilla.org/show_bug.cgi?id=1804067

Honza
Employee
Employee
ldetomi
New member

@HonzaYes but... after almost 4 years no answers there (effectively is not so clear why exist these two website that seem to have the same purpose), so I tried again here, hoping in a new attention

Honza
Employee
Employee

Yes, I understand the frustration. Some things are just taking too long.

Thank you for the report in any case!

spencerthayer
New member

I added a similar request to this one, which you can find here. It is rather disheartening to see that this is an issue that the Firefox team has had an opportunity to resolve but simply has been ignoring for years now.