Then tell me why turning 'on for all pages' causes firebug to fail to turn on while browsing in firefox?
Can you confirm that by turning 'on for all pages', firebug stays on for every single page until you explicitly turn it off? On Jul 1, 8:31 pm, johnjbarton <johnjbar...@johnjbarton.com> wrote: > On Jul 1, 6:41 pm, jjj <jason31...@gmail.com> wrote: > > > Sorry, let me rephrase that. > > > Since firebug is an "add-on" for Firefox, this keyboard accelerator is > > actually "Ctrl+N" (Or otherwise via File->New Window). Perhaps you're > > forgetting that firebug runs in Firefox? Therefore any accelerator > > keyboard commands that the add-on "overloads" or "replaces" should be > > firebug's responsibility. > > To the best of my knowledge Firebug does not overload or replace > control n. > > > > > Perhaps you should try a simple test-case instead of complaining that > > "Ctrl+N" is not part of firebug, and instead try to understand that > > its a regression design decision, and with that decision, there is no > > affordance in the new version to 1.) match previous firebug UI > > behaviors and expecations and 2.) Firefox plugin standards for > > enabling/disabling an add on - Perhaps evaluate how the flashblock add- > > on functions for a definition of enabled/disabled? > > Since Firebug did not overload or replace control n in the past or > present I don't now how to help you. > > jjb --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to firebug@googlegroups.com To unsubscribe from this group, send email to firebug+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
