Sounds like issue 1894 http://code.google.com/p/fbug/issues/detail?id=1894 which I fixed last week. Its no in 1.4b3.
jjb On Jun 30, 2:07 pm, Pappy <[email protected]> wrote: > Step-by-step: > > OS X: 10.5.7 > Firefox: 3.5 Release > Firebug: 1.4.0b3 > > - Start Firefox with a clean profile (Firefox -P) > - Browse tohttp://getfirebug, install Firebug, restart Firefox > - On "http://www.mozilla.com/en-US/firefox/central/";, right-click on > "Some of our favorite sites", select "Inspect Element" > - Change the 'margin-top' value (eg. select it and press up-arrow). > Note margin doesn't actually seem to change. > - Click off the CSS editing area. Notice the key you were just > editing disappears, as well as the rule description for that block. > > Just to be clear, this is happening for any page and any html element > for me. > > On Jun 30, 11:54 am, johnjbarton <[email protected]> wrote: > > > We need test cases. > > jjb > > > On Jun 30, 10:58 am, Pappy <[email protected]> wrote: > > > > Just to add another two proof points, a co-worker and I see the exact > > > same issue with FF 3.5 and FB1.4.0b3. > > > > On Jun 30, 10:31 am, "brian.tully" <[email protected]> wrote: > > > > > Wow - I'm having the same exact issue based on your screencast. Very, > > > > very, odd. Tried reinstalling Firebug to no avail. I definitely don't > > > > have 2 copies of the same stylesheet. This just started happening > > > > yesterday and it's really thrown a monkey wrench into my dev flow. I > > > > am so dependent on Firebug it's not funny. I've been forced to use > > > > Safari 4's web inspector, but I really hope there is a fix for > > > > Firebug. > > > > > FWIW I'm using FF 3.0.11 and Firebug 1.3.3 on Mac OS X 10.5.7 > > > > > On May 12, 12:11 pm, Kyle Hayes <[email protected]> wrote: > > > > > > Here is a screencast to show what is > > > > > happening:http://screencast.com/t/omNzONF0hyz > > > > > > On May 12, 9:09 am, Kyle Hayes <[email protected]> wrote: > > > > > > > I'm very saddened to report that this didnotwork. I just now tried > > > > > > it and I am getting the same issue as before. > > > > > > > On May 12, 8:50 am, johnjbarton <[email protected]> wrote: > > > > > > > > Try a new Firefox > > > > > > > profile:http://groups.google.com/group/firebug/web/faq-about-firebug > > > > > > > bet that fixes it. > > > > > > > > jjb > > > > > > > > On May 12, 8:48 am, Kyle Hayes <[email protected]> wrote: > > > > > > > > > FF v.3.0.10 > > > > > > > > FB v.1.3.3 > > > > > > > > > All of the suddenCSSdebugging stoppedworkingand I'm no longer > > > > > > > > able > > > > > > > > to change properties on the fly. If I do try to change a > > > > > > > > property and > > > > > > > > escape out of the editing, the selector disappears. There just > > > > > > > > seems > > > > > > > > to be a lot of issues with theCSSpane all of the sudden. > > > > > > > > > I've restarted fb/ff, and I've also attempted > > > > > > > > uninstallingfirebugand > > > > > > > > reinstalling it. > > > > > > > > > Any ideas? > > > > > > > > -Kyle --~--~---------~--~----~------------~-------~--~----~ 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 http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
