Bug 28813 – REGRESSION: Debugger no longer lists all script sources

• Status: RESOLVED
• Resolution: FIXED
• Component: Web Inspector (Deprecated)

[Oliver Hunt]

The debugger no longer lists the full set of scripts that are available.

To Reproduce:
1. Go to http://testsuites.opera.com/JSON/correctness/004.html
2. Enable debugging
3. Look at the JS code drop down in the debugger window

In r47839 there are only 3 entries:
(program)
004.js
common.js

In 4.0.3 there is also
004.html (as this has script as well)

[Pavel Feldman]

In addition to the problem reported, scripts do not have content available. The reason is that scripts are being reported as parsed prior to corresponding resources being reported as loaded. As a result, wrong viewer is being instantiated for the resource (resource type is "Other" during the parsedScript invocation).

[SubresourceLoader:137] m_client->didReceiveResponse(this, r); 
leads to InspectorController::didParseSource call, whereas

[SubresourceLoader:142] ResourceLoader::didReceiveResponse(r);
leads to the InspectorController::didReceiveResponse notification.

Frontend should either expect this order of events or notifications order should be fixed.

Timothy, what is your view on this?

[Timothy Hatcher]

Yes, that is a correct diagnosis. This has been an issue from the beginning in some cases. But maybe it happens more now.

I think we can fix it either way. Might be easier to fix the order the InspectorController is notified.

[Jon Evans]

I think I'm seeing this bug. Scripts appear in the drop-down but don't display when you select them. Really frustrating if you're following code paths that span different js files.

Sometimes reloading the page helps, but not always.

[Timothy Hatcher]

*** Bug 31230 has been marked as a duplicate of this bug. ***

[Alexey Proskuryakov]

See also: bug 30506.