[Webkit-unassigned] [Bug 50432] Web Inspector: inline script blocks and injected script elements don't show "scripts" tab list

Fri Dec 3 08:15:41 PST 2010

https://bugs.webkit.org/show_bug.cgi?id=50432

--- Comment #3 from Pavel Feldman <pfeldman at chromium.org>  2010-12-03 08:15:41 PST ---
(In reply to comment #2)
> You can get "scripts" which otherwise are not shown in the scripts drop-down, to be shown, in Safari, by adding to your script, a comment of the form:
> 
>    //@sourceURL=name-of-the-script.js
> 
> Does not work in Chrome Dev Tools (never did, IIRC).
> 

Wrong. Works for a year or so in Chrome DevTools.

> It should also be the case that if you can get the debugger to stop in one of these un-shown scripts, that while the debugger is stopped there, a script entry is added to the drop-down with the name "(program)".
> 
> We tried earlier to just show all the script entries, and for apps that load scripts dynamically (via eval()), the drop-down became a sea of unfriendly "(program)" entries.  Be careful what you ask for.  :-)
> 
> The whole concept of "scripts" in the browser environment is a bit squirrelly to begin with ...

I don't see what's wrong with it. There is a known issue with dynamically added scripts via <script> and document.write that needs to be fixed. There was a nice idea of showing origin of the script (i.e. resource, tag or document.write) that got stuck somewhere half way. We just need to finish it.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.