I'm not sure if this is the place to propose / suggest this, but as an avid user of the Firebug add-on, I thought at minimum the ideas I have might reach someone who might one day implement them...
1.) When working on a site, I often make changes and then click refresh whereby what was the current location or highlighted section of code seen in Firebug often becomes "reset" back to the body element... I.e. - suppose you're working on something in Firebug on line 452... If you make changes to something and then click the refresh button in the browser, Firebug often resets its location or focus back on to the body element, forcing you to click through all the collapsed blocks of code to return to where you were... This needs to be changed. If someone refreshes the page, wouldn't be cool to be EXACTLY where you were so that you can see what kinds of impact your change had on the code you were working on? From everything I've seen out of Firebug, there is not yet a way to preserve the focus / active section or location of code someone is working on. Firebug should maintain its location on the element you're working on and if you're working on the very line Firebug is focused on, then Firebug should instead move its focus back to the containing parent of the element you were working on upon hitting refresh. 2.) I'm not sure if it's the Web Developer's extension or Firebug, but using "CTRL + ALT + Y" allows developers to select certain pieces or sections of a page in order to retrieve information about that element (i.e. - the styles being used). It would be awesome if Firebug put our focus on that specific element's code block within the Firebug UI because right now, it only seems to "attempt" to highlight the element--not necessarily place cursor focus on it or its parent... 3.) When using the Firebug UI, I've often made markup or CSS changes in it to "test" certain effects before implementing the actual code. For example, I often do this with CSS: I'll use the "CTRL + ALT + Y" selection method to find the element and then using the UI, I'll make the CSS change I'm wanting to try in order to see if the change works or not. If it does, I then go to my actual code editor and make the respective change... What would be nice about all this is if the change you add / try from the UI provides an option to maintain the state of the change upon hitting refresh (i.e. - say you make a change in the UI and you want that change to be there after hitting the refresh button). -- 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
