Customize keyboard shortcut Shift+F12

67 views
Skip to first unread message

K

unread,
Jan 8, 2012, 4:23:29 AM1/8/12
to fir...@googlegroups.com
I'm glad that Firebug finally adds keyboard shortcut to deactivate (rather than simply minimize) Firebug: Shift+F12. However, I do not find a way to customize it. Will this be added to in the future versions?

BTW, how much overhead is it to leave Firebug active for all websites, in compare to deactivate Firebug by default and only activate it when I use? If Firebug consumes much CPU and memory, I have to deactivate it all the time.

Thanks for help!

Sebo

unread,
Jan 9, 2012, 7:48:23 AM1/9/12
to fir...@googlegroups.com
I'm glad that Firebug finally adds keyboard shortcut to deactivate (rather than simply minimize) Firebug: Shift+F12.
This shortcut is already available since Firebug 1.5.
 
However, I do not find a way to customize it. Will this be added to in the future versions?
When you create an issue for it, then yes. :-)

BTW, how much overhead is it to leave Firebug active for all websites, in compare to deactivate Firebug by default and only activate it when I use? If Firebug consumes much CPU and memory, I have to deactivate it all the time.
As long as Firebug is deactivated for a website the overhead is minimal (it's just checking, if it should be activated for the website).
Also we're working hard on reducing the memory footprint of Firebug as well as increasing its performance when it's activated for a page.

Sebastian

Simon Lindholm

unread,
Jan 10, 2012, 10:50:26 AM1/10/12
to fir...@googlegroups.com
As long as Firebug is deactivated for a website the overhead is minimal (it's just checking, if it should be activated for the website).
Really? I was under the impression that JSD activation was global, so that Firebug slows the whole browser down even if it is only active in a single tab. This commit and related issues comes to mind, but I then don't actually know that code.

- Simon

Sebo

unread,
Jan 11, 2012, 1:27:18 AM1/11/12
to fir...@googlegroups.com
As long as Firebug is deactivated for a website the overhead is minimal (it's just checking, if it should be activated for the website).
Really? I was under the impression that JSD activation was global, so that Firebug slows the whole browser down even if it is only active in a single tab. This commit and related issues comes to mind, but I then don't actually know that code.
I thought there were changes recently, that deactivate JSD when switching to a tab, in which Firebug is not active. I don't have insight into the JSD code as well, so I could be wrong. Probably Honza can clarify that.

Sebastian
 

Jan Honza Odvarko

unread,
Jan 11, 2012, 1:38:29 AM1/11/12
to fir...@googlegroups.com
Simon is right, JSD is global so, if it's active it has an impact on the whole browser (on all opened browser windows).
Honza

Sebo

unread,
Jan 11, 2012, 4:29:25 AM1/11/12
to fir...@googlegroups.com
Simon is right, JSD is global so, if it's active it has an impact on the whole browser (on all opened browser windows).
I guess "active" means halted at a breakpoint? E.g. if I set a breakpoint inside a function called via setTimeout() and switch to another tab while the timeout is not finished yet, script execution won't stop. So I assume JSD is deactivated when you switch to another tab while script execution is not halted. Is that correct?

Sebastian

Jan Honza Odvarko

unread,
Jan 11, 2012, 9:02:40 AM1/11/12
to fir...@googlegroups.com
On Wednesday, January 11, 2012 10:29:25 AM UTC+1, Sebo wrote:
Simon is right, JSD is global so, if it's active it has an impact on the whole browser (on all opened browser windows).
I guess "active" means halted at a breakpoint?
Active means JSD is on (ie. when the Console or Script panel is enabled)
 
E.g. if I set a breakpoint inside a function called via setTimeout() and switch to another tab while the timeout is not finished yet, script execution won't stop. So I assume JSD is deactivated when you switch to another tab while script execution is not halted. Is that correct?
No, JSD is still on even if you switch to another tab.

Honza



Sebastian

Sebo

unread,
Jan 11, 2012, 9:13:54 AM1/11/12
to fir...@googlegroups.com
No, JSD is still on even if you switch to another tab.
Is there a reason why? Also is JSD really producing that much overhead?

Sebastian

Jan Honza Odvarko

unread,
Jan 11, 2012, 9:45:33 AM1/11/12
to fir...@googlegroups.com
On Wednesday, January 11, 2012 3:13:54 PM UTC+1, Sebo wrote:
No, JSD is still on even if you switch to another tab.
Is there a reason why?
Yes, because Firebug could be active on another tab (and in another window).
 
Also is JSD really producing that much overhead?
Firebug is utilizing JSD.pause if Firebug is deactivated for the current site.
Paused JSD should not produce that much overhead (recently fixed by Boris),
but I never tested it (but yes, still global).

Honza

 
Sebastian

K

unread,
Jan 12, 2012, 1:59:08 AM1/12/12
to fir...@googlegroups.com

When you create an issue for it, then yes. :-)

Sebo

unread,
Jan 12, 2012, 2:15:52 AM1/12/12
to fir...@googlegroups.com
On Wednesday, January 11, 2012 3:13:54 PM UTC+1, Sebo wrote:
No, JSD is still on even if you switch to another tab.
Is there a reason why?
Yes, because Firebug could be active on another tab (and in another window).
But while it's still active in another tab or window, what does JSD do in that tab? Breaks currently don't happen while you're not at that tab. The Console panel should not use JSD by default. So what's holding us from completely deactivating it in that case?
 
Also is JSD really producing that much overhead?
Firebug is utilizing JSD.pause if Firebug is deactivated for the current site.
Paused JSD should not produce that much overhead (recently fixed by Boris),
but I never tested it (but yes, still global).
Thanks for clarifying.

Sebastian

Jan Honza Odvarko

unread,
Jan 12, 2012, 4:51:42 AM1/12/12
to fir...@googlegroups.com
On Thursday, January 12, 2012 8:15:52 AM UTC+1, Sebo wrote:
On Wednesday, January 11, 2012 3:13:54 PM UTC+1, Sebo wrote:
No, JSD is still on even if you switch to another tab.
Is there a reason why?
Yes, because Firebug could be active on another tab (and in another window).
But while it's still active in another tab or window, what does JSD do in that tab?
E.g. intercepting all new scripts that could be created.

If you switch off JSD, you loose all debugging script info and you need to reload the page to get it back.


Breaks currently don't happen while you're not at that tab. The Console panel should not use JSD by default.

Sebo

unread,
Jan 12, 2012, 8:00:41 AM1/12/12
to fir...@googlegroups.com
On Thursday, January 12, 2012 10:51:42 AM UTC+1, Jan Honza Odvarko wrote:
On Thursday, January 12, 2012 8:15:52 AM UTC+1, Sebo wrote:
On Wednesday, January 11, 2012 3:13:54 PM UTC+1, Sebo wrote:
No, JSD is still on even if you switch to another tab.
Is there a reason why?
Yes, because Firebug could be active on another tab (and in another window).
But while it's still active in another tab or window, what does JSD do in that tab?
E.g. intercepting all new scripts that could be created.

If you switch off JSD, you loose all debugging script info and you need to reload the page to get it back.
OK. So turning it off completely is obviously not an option as long as the Script panel is enabled. And I guess this won't change with JSD2.
 
Breaks currently don't happen while you're not at that tab. The Console panel should not use JSD by default.
Yes, I read that in issue 4978, just linked my text incorrectly before. So hopefully it will be fixed soon.

Sebastian

Reply all
Reply to author
Forward
0 new messages