I tried what you suggested and created a new profile, and I got the same issue. I then completely uninstalled FF 3.5 and reinstalled. I added only firebug and no other addons, and I got the same issue. I then posted it as an issue on the bug tracker page.
On Jul 10, 2:00 pm, johnjbarton <[email protected]> wrote: > I suggest you try installing Firebug in a new Firefox profile, > seehttp://groups.google.com/group/firebug/web/faq-about-firebug > > Sometimes other extensions or upgrading Firefox cause some mysterious > problems. Since these kinds of problems are too difficult to > investigate, starting fresh is the most practical solution. > > It that does not help, please post a detailed problem description to > our issues list. > > jjb > > On Jul 10, 10:24 am, Raphael75 <[email protected]> wrote: > > > I have the same issue. Today I upgraded to FF 3.5 and Firebug 1.4.0b7. > > Since then, when I set a breakpoint it doesn't break. Also, in the > > console when I try to run some functions they don't fire. > > > I'm the front end web programmer for billygraham.org. If you go to: > > >http://www.billygraham.org/default.asp > > > open firebug, put some breakpoints in the nb(dir) function (which > > changes the big image on the homepage), and try to execute nb('n') in > > the console, it won't fire. However, the crossfade function (example: > > crossfade('vidtn0','vidtn0desc',1) ) does work in the console. > > > I've noticed that if I type something in the console and switch to > > another tab, and then switch back, what I typed is gone. > > > Also, the console doesn't seem to be remembering all the stuff you've > > previously typed (by pressing the up arrow to scroll through > > previously-typed items) > > > Thanks. > > > On Jul 10, 11:15 am, RichB <[email protected]> wrote: > > > > Thanks, > > > > I tried to develop a simplified test case, and it did break within the > > > script block without problem. I can't really submit my code at the > > > moment, but I'll keep an eye on things and submit when I have some > > > code that I can submit. > > > > Richard > > > > On Jul 10, 3:44 pm, johnjbarton <[email protected]> wrote: > > > > > If we had a test case we could fix > > > > it.http://code.google.com/p/fbug/issues/list > > > > jjb > > > > > On Jul 10, 1:55 am, RichB <[email protected]> wrote: > > > > > > sorry yes 1.4b7. I've actually externalised the javascript now, and it > > > > > breaks without problem, though seems to require it to be already > > > > > broken, or not started for a new breakpoint to be recognised. If the > > > > > js is within the html I cannot get it to break atall. > > > > > > Thanks, Richard > > > > > > On Jul 10, 6:36 am, johnjbarton <[email protected]> wrote: > > > > > > > Which version of Firebug? 1.4b7 is the version we are working on. > > > > > > jjb > > > > > > > On Jul 9, 8:08 am, RichB <[email protected]> wrote: > > > > > > > > I have written an html page and have javascript within the <head> > > > > > > > however if I place a breakpoint within this javascript the > > > > > > > breakpoint > > > > > > > is never triggered despite an alert immediately after being shown. > > > > > > > Should I expect it to be triggered, or is it only triggered within > > > > > > > external files? Do I need to change a setting if not? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
