Will the team accept this feature? If so, I might try to work on it.

A separate tab sounds good! Thank you.

Something like this?

I think having it as another field in the Headers tab (right above "Response headers") will be much more convenient to the developer - less context switching - and a popover is enough, as well as consistent (is there any other place that shows a full stack trace, beside the console?).

Since implementing it was so easy (half an hour, hehe), I will try and put it quickly in the Headers tab for experience comparison.

Deleted: network-initiator-tab.png 111 KB

	network-initiator-tab.png 111 KB View Download

This looks good. Requires a sentance of explanation though. It would be nice if method names were aligned to right though, with @ stacked vertically. I thought that was what standard stack renderer produced...

Going forward, users would want to see more here. Try holding shift and hovering over network log. It would show (highlight with color) which requests it initiated and which requests it is initiated by. So there is a sizeable potential to accompany this boring stack with some more fun info in the new tab. Let's say, it has three sections:

1) Full async initiator stack (your patch)
2) List of requests that led to this request initiation
3) List of requests it caused.

Each NetworkRequest sdk object has initiator chain, so should be super easy to implement.


As for headers vs separate tab, hover is less accessible both from general UX and a11y perspectives. You could hover to see it in the grid, you can switch to the tab for exanded stack.

If we rename Headers to Details, it would become appropriate and hover would work there, but it would be complementary to the separate tab.

Happy hacking!

Assigning