164427 2016-11-04 13:27:17 -0700 Web Inspector: WorkerTarget's mainResource should be a Resource not a Script 2016-12-13 15:37:14 -0800 1 1 1 Unclassified WebKit Web Inspector WebKit Nightly Build All All NEW InRadar P2 Normal --- 164425 1 joepeck webkit-unassigned inspector-bugzilla-changes webkit-bug-importer oldest_to_newest 1248237 0 joepeck 2016-11-04 13:27:17 -0700 Summary: WorkerTarget's mainResource should be a Resource not a Script This is the frontend portion once we address bug 164425. Currently, all Worker resource loads are RawResourceRequests. Such resources do not always get saved. In the past that was fine because they are typically ephemeral (XHR,Fetch, etc). However Worker resources are more like <script src="..."> and we should expect Web Inspector to be informed of them. This impacts Web Inspector in a few different ways: - If Web Inspector is opened after a page has loaded - Worker Script Resources are not guaranteed to exist so the frontend may not know about them - Worker Script Resources may show up as a Script instead of a Resource - being Script and not Resource, don't get a Resource Details Sidebar - being Script and not Resource, the Network tab won't have Resource load data - Web Inspector has a workaround converting the type from XHR -> Script in some places Notes: - WorkerScriptLoader issues ThreadableLoader requests that it knows will be Scripts. It would be good to type such requests as Script early on. 1248238 1 webkit-bug-importer 2016-11-04 13:27:29 -0700 <rdar://problem/29117462> 1248241 2 joepeck 2016-11-04 13:36:34 -0700 I have workarounds for most of these issues that merely check if the WorkerTarget's mainResource (a Script) has an associated Resource. But it would be nice to eliminate all of these workarounds in the frontend.