Open Bug 1092821 Opened 5 years ago Updated 7 months ago
Opening DOM Inspector is much faster than opening Browser Toolbox
This bug is about the time it takes from the point when you decide you want to inspect chrome to the point when you're up and inspecting. To inspect the main browser window: - with DOM Inspector, about 2 to 3 seconds - with Browser Toolbox, about 22 to 23 seconds Part of the time for Browser Toolbox is saying yes to the remote connection prompt. It would save a couple seconds if that prompt appeared on top, but right now it appears behind the toolbox window. I'd guess another big part of the delay is all that disk I/O on my non-SSD system. Developer Tools are really great and they've helped me solve several problems that would have been hard without them, but that's a big time difference.
FWIW, the prompt can be disabled via the devtools.debugger.prompt-connection pref (which I've added to this doc: https://developer.mozilla.org/en-US/docs/Tools/Browser_Toolbox). Bug 1031404 won't completely solve the rest of this, but I think that once it is resolved this would speed things up considerably since the debugger panel wouldn't have to initialize immediately if you had been using the Inspector last.
Depends on: 1031404
Component: Developer Tools: Inspector → Developer Tools: Framework
Bug 1013379 will also remove the need to set a pref in order to avoid the prompt.
Depends on: 1013379
As outlined in bug 1378964, the DOM Inspector can also be very slow. Sebastian
(In reply to Sebastian Zartner [:sebo] from comment #3) > As outlined in bug 1378964, the DOM Inspector can also be very slow. "DOM Inspector" in this bug is talking about the separate extension by that name which was used for debugging the browser chrome.
(In reply to Matthew N. [:MattN] (huge backlog; PM if requests are blocking you) from comment #4) > (In reply to Sebastian Zartner [:sebo] from comment #3) > > As outlined in bug 1378964, the DOM Inspector can also be very slow. > > "DOM Inspector" in this bug is talking about the separate extension by that > name which was used for debugging the browser chrome. Ah, I totally missed that. Thanks for the clarification! Sebastian
You need to log in before you can comment on or make changes to this bug.