Excellent, thanks for the update! Note that the patch will be included in the next (minor) release: Firebug 2.0.2
Honza On Wednesday, July 2, 2014 5:31:59 PM UTC+2, Ivan Gomes wrote: > > @Honza: Works wonderfully! Thank you. > @Eugene: I meant that dynamically loaded scripts were showing, but the > display was different so I wasn't sure. But as of Honza's last post, I > would recommend downloading the latest .XPI provided and installing it. > > On Wednesday, July 2, 2014 10:54:37 AM UTC-4, Eugene Choi wrote: >> >> when you say some success, do you mean you can reliably use that version >> of the plugin, or is it hit and miss? at this point, i am content w/ >> rolling back to a prior version, bc i can't afford this hangup at work... i >> might be willing to switch if it's 100% reliable with viewing all >> javascript and debugging >> >> On Wednesday, July 2, 2014 7:49:44 AM UTC-7, Ivan Gomes wrote: >>> >>> I seem to be having some success with the latest FF and FireBug 2.0b8. >>> You can easily install at the Firefox Addons version history page >>> <https://addons.mozilla.org/en-US/firefox/addon/firebug/versions/>, and >>> it doesn't require a browser restart. Has anyone found problems with this >>> approach? >>> >>> On Wednesday, July 2, 2014 10:21:32 AM UTC-4, Eugene Choi wrote: >>>> >>>> I am having same problem with any version of FF 30+ && Firebug 2.0+. >>>> >>>> i reverted back to FF 29 && Firebug 1.12. >>>> >>>> i turned off FF's autoupdate so that it doesn't push me to FF 30. >>>> >>>> this is very disappointing to see problems with Firebug 2.0 when >>>> previous releases haven't had a major flaw like this. I almost gave up on >>>> FF+FB for Chrome! >>>> >>>> On Friday, June 13, 2014 6:22:50 AM UTC-7, Raul Marzo wrote: >>>>> >>>>> Hi. >>>>> >>>>> I've been using Firebug for debugging javascript for years, and there >>>>> wasn't any problem to see the source of any file downloaded >>>>> asynchronously >>>>> from the script tab in Firebug, like libs using AMD. Not until I upgraded >>>>> to Firefox 30 and Firebug 2.0. After the upgrade, I can't see any source >>>>> files downloaded async, and debugging is completely impossible for those. >>>>> As you can see in the attachments, the number of files I can choose in >>>>> the >>>>> script tab is nowhere close to what it was before. >>>>> >>>>> Does anybody know if is there any Firebug setting that would restore >>>>> the old behaviour regarding the script tab? Otherwise I see myself having >>>>> to move to Chrome, which I would like to avoid as there is always small >>>>> differences between the two, and a co-worker already uses Chrome for >>>>> debugging. >>>>> >>>>> Thanks in advance. >>>>> >>>>> *Confidentiality Notice:* - This message and any attached files may >>>>> contain information that is confidential and/or subject of legal >>>>> privilege >>>>> intended only for the use by the intended recipient. If you are not the >>>>> intended recipient or the person responsible for delivering the message >>>>> to >>>>> the intended recipient, be advised that you have received this message in >>>>> error and that any dissemination, copying or use of this message or >>>>> attachment is strictly forbidden, as is the disclosure of the information >>>>> therein. If you have received this message in error please notify the >>>>> sender immediately and delete the message. >>>>> >>>>> -- 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/b7f0e0e5-c12e-422e-b40a-f90921b6f9a5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
