Closed Bug 976718 Opened 10 years ago Closed 9 years ago

connect a request in the netmonitor to whatever code initiated that request

Categories

(DevTools :: Netmonitor, defect)

16 Branch
x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 906239

People

(Reporter: canuckistani, Unassigned)

Details

As a developer I sometimes get confused as to where exactly a request is coming from, especially in large applications or situations where I'm using a complex framework. I'd like to be able to easily get form the request item in netmonitor to the file / line where that request started:

* for css files, the html link or style tag
* for js files, the script tag or xhr
* for images, the img tag or related js code
* for JSON, the xhr

For bonus points if we had tag stack we could provide a stack of any async calls that result in something being loaded, from the initial code to the callback's completion ( or the promise chain, or... )

Aside: It feels like linking from a css file to an import() or <link> ( or in JS from a script tag, or with images from an img tag ) could be done in a relatively straightfoward way - I'd consider this a viable first version if we needed to wait for tagStack in order to provide really good support for resources loaded by JS in various ways.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
(In reply to Jeff Griffiths (:canuckistani) from comment #1)
> 
> *** This bug has been marked as a duplicate of bug 906239 ***

This one seems much more general than bug 906329, since it discusses much more than XHR / Ajax requests.
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.