More good news, the dojo team fixed their source URL syntax a few days ago:
https://github.com/dojo/dojo/commit/06f4b6f2e4b6a57944251f7d242b6751520de937 So this problem should be gone with the next release of dojo. Sebastian On Wednesday, September 10, 2014 2:45:56 PM UTC+2, Sebastian Zartner wrote: > > We are using a Firefox API, which is broken for source URL definitions > with four slashes. I reported that in bug 1065259 > <https://bugzilla.mozilla.org/show_bug.cgi?id=1065259>. > Additionally I created issue 7656 > <https://code.google.com/p/fbug/issues/detail?id=7656> for this in our > tracker and created a patch for it (and two other issues) in issue 7201 > <https://code.google.com/p/fbug/issues/detail?id=7201> fixing this on the > Firebug side. > > Sebastian > > On Tuesday, September 9, 2014 8:23:01 PM UTC+2, ed wrote: >> >> I'd love to, but it's dojo adding the ////@ sourceURL, not me. >> >> On Sunday, September 7, 2014 6:43:57 PM UTC-4, Sebastian Zartner wrote: >>> >>> Remove two of the slashes at the beginning and you should be good to go. >>> Source URLs generally look like this: >>> >>> //@ sourceURL=/path/to/the/file.js >>> >>> or >>> >>> //# sourceURL=/path/to/the/file.js >>> >>> Source URLs within new Function() constructs are not recognized yet >>> <https://code.google.com/p/fbug/issues/detail?id=7201>, though that >>> shouldn't affect your Dojo code. >>> >>> Sebastian >>> >>> On Thursday, September 4, 2014 3:57:50 PM UTC+2, 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 firebug+unsubscr...@googlegroups.com. To post to this group, send email to firebug@googlegroups.com. 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/e85c6072-d257-4d65-832f-d5bdc6b536a8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
