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

Fri Dec 3 14:48:14 PST 2010

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

--- Comment #6 from Patrick Mueller <pmuellr at yahoo.com>  2010-12-03 14:48:14 PST ---
(In reply to comment #3)
> > 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.

Here's the thing.  JavaScript source gets injected into the browser in a bunch of ways: <script> tags, onXXX handlers, eval(), Function(), bookmarklets.  Looking a little wider, I can use SWT's WebKit interface to run arbitrary JS code from Java - not sure what kind of context that runs under.  Etc.

Do we want to show all these little JS bits as separate "scripts".  As I mentioned, there were already issues regarding extension (Program) entries when your app loads lots of JS files via XHR (or whatever).  

I guess my point is, it's not clear to me that the current way we expose "scripts" - a simple drop down list - really scales to all the places that folks might need it.  Perhaps there is a better way.  Show scripts in a richer tree-like structure or something like we do other non-trivial collections of things (eg, resources)

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