It also seems that once you check "On for all pages" on a browser session, thre is no way to disable it (unchecking doesn't work, you can "close" firebug, but it opens again on the next page load).
On Jul 2, 3:33 pm, sir_brizz <bj.car...@gmail.com> wrote: > I assumed his test case was pretty self explanatory. > > 1) Right click Firebug, check "On for all pages". > 2) Hit Ctrl-N (or whatever your key combo for a new window is) > -- Firebug is not enabled on the ensuing home page load and "On for > all pages" is not checked. > > In his other scenario: > 1) Right click Firebug, check "On for all pages". > 2) Minimize Firebug. > 3) Browse to another page on any domain. > -- Firebug panel pops open instead of staying minimized. > > On Jul 2, 3:16 pm, johnjbarton <johnjbar...@johnjbarton.com> wrote: > > > I assume from your reply that you found my test sequence to work > > properly on your machine. That's good. You are welcome to propose your > > own test sequence either here or on the bug report. When you do I will > > try it. > > jjb > > > On Jul 2, 12:47 pm, jjj <jason31...@gmail.com> wrote: > > > > No, this test case does not take into account the following failures: > > > 1.) the firebug panel fails to be enabled when launching new firefox > > > windows by going to File->New Window in Firefox. Defect. > > > > 2.) the firebug panel-reopens every time you navigate to a new page. > > > There is no configuration affordance or set of options that will allow > > > firebug to be enabled (i.e. script, network, or other data > > > monitoring), but not UI-invasive when not needed. This is a regression > > > design decision. > > > > A user story would be: I really want to have firebug monitoring all > > > network requests but not be visible until I determine there has been a > > > need to view the webpage, for instance to check on AJAX requests, or > > > some similar need to view all the requests a webpage has made from the > > > first load to when the panel has been opened. > > > > Thanks, > > > J > > > > On Jul 2, 8:49 am, johnjbarton <johnjbar...@johnjbarton.com> wrote: > > > > > On Jul 2, 8:20 am, jjj <jason31...@gmail.com> wrote: > > > > > > Then tell me why turning 'on for all pages' causes firebug to fail to > > > > > turn on while browsing in firefox? > > > > > I don't know why this does not work for you. It works for me. > > > > > > Can you confirm that by turning 'on for all pages', firebug stays on > > > > > for every single page until you explicitly turn it off? > > > > > I can confirm that Firebug will stay on for me if I select "on for all > > > > pages" then visit a set of completely different sites. > > > > > Here is are the specifics: > > > > 1) Open Firefox 3.5 with Firebug 1.5a7. > > > > 2) Right click Firebug Icon, select On for all Web Pages. > > > > 3) Openwww.google.comfirebugisup > > > > 4) search for "foo" and click on the first > > > > result,http://en.wikipedia.org/wiki/Foo; > > > > Firebug is up. > > > > 5) typehttp://www.ibm.comintothelocationbar, hit enter. Firebug > > > > is up > > > > > Does this work for you? > > > > > Based on my tests and the fact that other users have used this option > > > > successfully, it's my guess that the reason it fails for you is > > > > related to some property of your environment. A simple and effective > > > > test for this is create a new Firefox profile, install Firebug, and > > > > restart. > > > > > 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 -~----------~----~----~----~------~----~------~--~---
