Bug 35744 - Web Inspector: display worker scripts being loaded in resources panel
Summary: Web Inspector: display worker scripts being loaded in resources panel
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: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-04 07:00 PST by Andrey Kosyakov
Modified: 2010-03-08 11:43 PST (History)
8 users (show)

See Also:


Attachments
Enable resource loading progress callbacks when loading workers (1.59 KB, patch)
2010-03-04 07:18 PST, Andrey Kosyakov
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Kosyakov 2010-03-04 07:00:41 PST
Scripts loaded during worker creation or in worker's context importScript() should be shown in Resources panel, similar to scripts loaded by other means.
Comment 1 Andrey Kosyakov 2010-03-04 07:18:23 PST
Created attachment 50015 [details]
Enable resource loading progress callbacks when loading workers
Comment 2 Eric Seidel (no email) 2010-03-05 13:15:04 PST
Comment on attachment 50015 [details]
Enable resource loading progress callbacks when loading workers

OK.
Comment 3 WebKit Commit Bot 2010-03-05 23:11:26 PST
Comment on attachment 50015 [details]
Enable resource loading progress callbacks when loading workers

Clearing flags on attachment: 50015

Committed r55612: <http://trac.webkit.org/changeset/55612>
Comment 4 WebKit Commit Bot 2010-03-05 23:11:31 PST
All reviewed patches have been landed.  Closing bug.
Comment 5 Alexey Proskuryakov 2010-03-08 11:43:07 PST
Comment on attachment 50015 [details]
Enable resource loading progress callbacks when loading workers

+        Enable resource loading callback while loading worker scripts
+        https://bugs.webkit.org/show_bug.cgi?id=35744

The line above bug URL should say "Web Inspector: display worker scripts being loaded in resources panel", because that's what being fixed here. How the result is achieved goes to per-function comments below.

The reason for this is that someone reading commit e-mails (or subversion logs) shouldn't need to open a bug to find out why a change was made.