Firebug is maintained by a handful of people 
<https://github.com/firebug/firebug/graphs/contributors?from=2013-09-09&to=2014-09-08&type=c>,
 
which simply can't check every possible configuration and therefore need 
your help when you stumble over a problem. If it's not hard to reproduce, 
then please file a bug <https://code.google.com/p/fbug/issues/entry> and 
attach a simple test case to it, so it can be fixed.

Sebastian

On Thursday, September 4, 2014 4:13:58 PM UTC+2, Eugene Choi wrote:
>
> Use Chrome at this point. I've pretty much given up on FF+Firebug until 
> they play nicely. I've seen much inconsistent behavior that it's more 
> hassle than help to live thru the problems, and just use chrome until FF+FB 
> are good again. Who knows if it's a FF or FB problem at this point.  I'm 
> surprised the FB developers don't see the stuff we are seeing as users, 
> it's not that hard to reproduce
>
> On Thursday, September 4, 2014 6:57:50 AM UTC-7, ed wrote:
>>
>> I was just updated to Firefox 31.0 ESR and Firebug 2.0.3 and all the 
>> script dynamically loaded by dojo appear in the Scripts drop-down list as
>> dojo.js.uncompressed.js...line 16557 > eval (156)
>> or something similar. To make matters worse, if I manage to find the file 
>> I'm looking for I cannot set a breakpoint on any of the source lines.  The 
>> files all have 
>> ////@ sourceURL=/path/to/the/file.js
>> at the bottom.
>>
>> Is there anything I can do? I'm dead in the water.
>> --ed
>>
>> On Friday, June 13, 2014 9:22:50 AM UTC-4, 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/693ddb41-dd19-41df-8de8-027a8673d6e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to