Bug 148487

Summary: JSContext Inspector: Add Resources scope bar to filter anonymous/named scripts
Product: WebKit Reporter: Blaze Burg <bburg>
Component: Web InspectorAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WORKSFORME    
Severity: Normal CC: bburg, graouts, joepeck, mattbaker, nvasilyev, timothy, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: All   
OS: All   

Blaze Burg
Reported 2015-08-26 11:58:01 PDT
There could easily be a barrage of anonymous scripts, might want to filter those out.
Attachments
Radar WebKit Bug Importer
Comment 1 2015-08-26 11:58:28 PDT
Nikita Vasilyev
Comment 2 2016-03-01 00:10:09 PST
Could you provide steps to inspect JSContext?
Joseph Pecoraro
Comment 3 2016-03-01 12:06:10 PST
(In reply to comment #2) > Could you provide steps to inspect JSContext? To inspect a JSContext, create an OS X Application that links JavaScriptCore.framework and creates a JSContext. Remember to add the "com.apple.security.get-task-allow" entitlement so that it can be remotely debugged by Safari.
Joseph Pecoraro
Comment 4 2016-03-01 12:08:40 PST
(In reply to comment #0) > There could easily be a barrage of anonymous scripts, might want to filter > those out. I'm not sure I understand the concern. What types of anonymous scripts do you expect will show up in a JSContext? Currently a JSContext inspector will only show named scripts. For example: - -[JSContext evaluateScript:withSourceURL] - JSEvaluateScript(...sourceURL...) - script with "//# sourceURL=name" directive All other scripts won't appear by default, and I'm not sure they can be made to show. Perhaps this bug is behaves correctly?
Note You need to log in before you can comment on or make changes to this bug.