Hi Guys, First of all let me thank you for this great add-on, it is really something that you can't live without if you are a dev. (Not sure why firefox implements it's own inspect element, it should instead include this add-on by default and let those do the job who know what and how to do it :) )
So now back to the bug report, I have the following problem: Scenario ======= I always use Firebug in a separate window, so just simply right click on any part of the website, select Inspect element and it popups the new window with Firebug started. This is just great, exactly as I want but now I visit another website and the Firebug window of course is open (which is just fine) and so on the new website I also activate Firebug and do my job. Now if I deactivate firebug for this website and close down the window (or just close down the window) and move back to my first website Firebug is running in the background and there is now window nor a firebug attached to the website (not detached) so I simply think that Firebug is deactivated for that website too but in reality it is running in the background and you have no idea unless you activate it again and then the new window will show up with Firebug already activated. Duplicate ======= 1. Open a new Firefox tab and go to google.com 2. Activate Firebug and detach it from the Firefox window 3. Open a new tab and go to getfirebug.com 4. Activate Firebug and it should open in the detached window 5. Deactivate Firebug and close the window (or just simply close the window) What happens =========== Firebug is still running in the background but not showing itself nor in a new window (because we just closed it) nor does it show in an attached state to the Firefox window. For e.g. Go back to the first tab (google.com) and you will see no Firebug window nor Firebug attached to the Firefox window but Firebug is still running in the background. To confirm this just load about:home in the tab and enter something to search for and if you click search you will see it takes a lot of time to go to google and the Processor usage will go up because Firebug in reality is running in the background and is processing the google search page as you are redirected from about:home to google search. What Should happen =============== I think the best way to handle this would be to reattach the Firebug window to the Firefox window if Firebug not deactivated but it's window closed. This way one would see that the Firebug is still active for the website and won't leave it like that by mistake if using a lot of tabs. Also I think it would be important to still show Firebug in a new window if one loads a website in a new tab that doesn't have Firebug activated for it and activates it as if we just simply revert back to attached mode one would have to again detach it manually. So bottom line, if in detached mode and no window found but Firebug active show it as attached but as soon as there is a detached window for Firebug move the attached to the existing window. System Tested on ============= Linux/Fluxbox/Firefox 16.0.2 Firebug 1.10.6 Hope everything is clear and this hasn't been posted as a duplication, I tried to search for deactivating firebug for all websites and so on but I only found entries when one wants to deactivate Firebug from javascript :) but please let me know if this has been handled in the new beta or if there is a fix for it already available. Thanks in advance and please don't hesitate to ask for any more information if needed or for help on any part of making this fix happen. Regards, Julius -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at https://groups.google.com/forum/#!forum/firebug
