Bug 40220 - Web Inspector: should be possible to distinguish extension scripts from main world scripts
Summary: Web Inspector: should be possible to distinguish extension scripts from main ...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (Deprecated) (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Yury Semikhatsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-07 01:26 PDT by Yury Semikhatsky
Modified: 2010-06-07 23:15 PDT (History)
8 users (show)

See Also:


Attachments
Patch (24.70 KB, patch)
2010-06-07 02:14 PDT, Yury Semikhatsky
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Yury Semikhatsky 2010-06-07 01:26:05 PDT
There are two types of scripts associated with web page: the scripts from the page itself and content scripts injected by browser extensions. There should be a way to discriminate between them in Web Inspector.
Comment 1 Yury Semikhatsky 2010-06-07 02:14:06 PDT
Created attachment 58002 [details]
Patch
Comment 2 Yury Semikhatsky 2010-06-07 02:58:22 PDT
Comment on attachment 58002 [details]
Patch

Clearing flags on attachment: 58002

Committed r60771: <http://trac.webkit.org/changeset/60771>
Comment 3 Yury Semikhatsky 2010-06-07 02:58:33 PDT
All reviewed patches have been landed.  Closing bug.
Comment 4 Timothy Hatcher 2010-06-07 19:49:32 PDT
Now that Safari has extensions, we should make this cross-browser not just Chromium.
Comment 5 Pavel Feldman 2010-06-07 23:01:48 PDT
(In reply to comment #4)
> Now that Safari has extensions, we should make this cross-browser not just Chromium.

Well, the point of this change was to make the functionality generic and available to Safari. Looks like Yury has implemented the JSC part and it should work for you already.
Comment 6 Yury Semikhatsky 2010-06-07 23:15:33 PDT
(In reply to comment #5)
> (In reply to comment #4)
> > Now that Safari has extensions, we should make this cross-browser not just Chromium.
> 
> Well, the point of this change was to make the functionality generic and available to Safari. Looks like Yury has implemented the JSC part and it should work for you already.

Yes, current implementation should work equally well in Safari.