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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Dec 2 20:38:37 PST 2010


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





--- Comment #1 from Kyle Simpson <getify at gmail.com>  2010-12-02 20:38:36 PST ---
It was noted by @thynctank that JSON-P polling creates lots of script DOM elements, with the potential to make that script list be unmanageably long. Of course, JSON-P script elements aren't of the sort I reported for this bug, but I think it's possible they are also not listed (currently) because they are added well after DOMContentLoaded/onload has passed. Am I correct in that assumption?

In any case, I think whether with JSON-P polling use case or not, stray (or temporary-use) script elements in the DOM should be cleaned up/removed after their purpose is served.

But it brings up the question as to whether or not scripts that have their DOM element removed should also be purged from the list of scripts or not. I can see both sides of the question.

On the one hand, you don't want the list of scripts to become unmanageably long from all those temporary-use script injections. On the other hand, once a script is injected into the page, just removing the element from the DOM does *not* remove it from the JavaScript environment. As such, perhaps those scripts should all stay listed since they are still in scope for the JavaScript context.

Perhaps the best way to handle this is to simply provide a way for the user to change a radio button to select "all", "external", "inline", etc for which scripts should be in shown in the list or filtered from the list. That seems like it might be the easiest way to serve all the use-cases.

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



More information about the webkit-unassigned mailing list