Bug 114969 – Web Inspector: //@ sourceURL does not work in new Function

• Status: RESOLVED
• Resolution: FIXED
• Component: Web Inspector (Deprecated)

[Timothy Hatcher]

This does not work:
new Function("console.log(1)//@ sourceURL=test1.js");

While this does:
eval("console.log(1)//@ sourceURL=test2.js");

From: https://twitter.com/PeterTheFace/status/326392487612657664

[Timothy Hatcher]

It works in Chrome/V8.

[Radar WebKit Bug Importer]

<rdar://problem/13707121>

[Peter Josling]

If the inspector is opened after the page has loaded then sourceURLs load fine, but if the page is refreshed when the inspector is already open, nothing. Similarly "new Function()" calls in the console have no effect (but eval() does).

[Timothy Hatcher]

It turns out this is hitting an optimization of the engine. We don't parse the script in the function until the function is called.

So to trigger it in the console you need to do:

new Function("console.log(1)//@ sourceURL=test1.js")();

I think this behaves correctly, even if there is a slight difference between Blink and WebKit.

Do you see this working in real life once the functions get called?

[Peter Josling]

If I paste that into my console I still don't see an entry for it in the resources pane, and on my test site none of the sourceURLs work even after the functions have been executed.

[Timothy Hatcher]

You are right. I was testing in Safari 6. This seems to have regressed since then and no longer works in the nightly.

[Timothy Hatcher]

THis was fixed by http://trac.webkit.org/changeset/152091.