sourceURL hint not working with dojo 1.5.0 and FireBug (1.6.1, 1.6.2, 1.70Xa9)

[reesd]

For some reason FireBug (1.6.1, 1.6.2, and 1.70Xa9) doesn't seem to using the sourceURL hint at the end of an eval when working with dojo 1.5.0. It lists the evals, but not with their filenames. And their content looks compressed with comments and white space removed. The debugger line works so it does know the right evals, just not its filename.

On the other hand, the same code is working in Chrome. Chrome shows the actual files in the scripts list, allows me to set breakpoints, and also stops at the debugger line.

I've stepped through the dojo code and I see its adding the sourceURL line. And since Chrome is working it seems there is enough information being given by dojo.

I have seen several posts from the past that say Firebug should just be working with evals and the sourceURL hint. Is there a trick I am missing?

Here are images of what I am seeing in FireBug and Chrome:

http://twitpic.com/3xawnf/full

http://twitpic.com/3xaxbo/full

http://twitpic.com/3xaxtu/full

http://twitpic.com/3xaxza/full

Thanks,
dave

PS, I've been using debugAtAllCosts in dojo (which switches the loader to using script insertion) which does give the line numbers, but that has some different drawbacks.It would be great if I could just get eval and sourceURL to work like it should (and does in Chrome).

[John J Barton]

If you post a test case I can investigate.
jjb

[David Rees]

Thanks, I appreciate it. Especially since I am sure it will come back to me
doing something wrong :/. I've seen a lot of people on the web with this
problem though, and no solutions other than debugAtAllCosts. If I hadn't see
Chrome working I would not have realized Firebug had this cool sourceURL
feature.

I've created issue http://code.google.com/p/fbug/issues/detail?id=4035 and
attached a zip file with the HTML/JS needed to see the problem. Hopefully
that is what you mean by a test case? If you need anything else just let me
know.

d

--
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To post to this group, send email to fir...@googlegroups.com.
To unsubscribe from this group, send email to
firebug+u...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en.

[reesd]

That to help from John I tracked down the issue. I had extensions.firebug.decompileEvals enabled ("Decompile for eval() source" on the scripts drop-down). So I guess Firebug was overwriting the source with its own decompiled version and somehow losing the filename along the way as well.

The next alpha is going to remove the "Decompile for eval() source" menu item from the GUI (see http://code.google.com/p/fbug/issues/detail?id=3731), so there be less chance of others folks seeing this issue. If you are seeing it, check extensions.firebug.decompileEvals in your about:config - you have set it in the past and forgot.

d

[reesd]

Note, in 1.7a10 the extensions.firebug.decompileEvals functionality will be removed completely. So if you are on 1.7a10 you shouldn't see this at all, and if you are you probably have a different problem :).