Thanks for the info. Unfortunately I'm still not able to reproduce this. I restarted the browser while the execution was halted at a breakpoint and the script was executed again after the browser restart and the contents within the <noscript> tag were not displayed. While a new profile may fix this problem, the upcoming version 2.0 of Firebug incorporates a new debugging engine, which will probably also fix this. Though this new version will probably at least require Firefox 30 and the next ESR version is 31, so that still takes a bit.
Sebastian On Friday, April 4, 2014 2:37:55 PM UTC+2, ed wrote: > > I think I figured out what causes this. If I have Firebug stopped at a > breakpoint and I close the browser, when I restert Firefox, script does not > run and the <noscript> elements on the page are rendered, but if I look at > about:cconfig, javascript.enabled is true. No amount of changing it from > true -> false -> true, closing and restarting firefox fixes it. I have to > create a new profile. > -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/14e8488c-2f5c-4c64-8251-263abeff337e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
