RESOLVED WONTFIX 167083
Web Inspector: capture async stack trace when web content calls addEventListener, window.postMessage, fetch, XHR.send 
https://bugs.webkit.org/show_bug.cgi?id=167083
Summary Web Inspector: capture async stack trace when web content calls addEventListe...
Blaze Burg
Reported 2017-01-15 14:50:00 PST
We should capture for more async script initiators. These are all for DOM methods.
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2017-01-15 14:50:12 PST
<rdar://problem/30033664>
Matt Baker
Comment 2 2017-04-22 21:17:53 PDT
It looks like DOMWindow already saves the call stack on postMessage (WebCore/page/DOMWindow.cpp:980), so long as the console agent is enabled. This is done so that if a target origin error occurs the console error can include a call stack. Instead of saving the call stack in the PostMessageTimer, DOMWindow should look up the current async stack trace using the InspectorDebuggerAgent.
Matt Baker
Comment 3 2017-07-21 19:27:28 PDT
Closing. This has been split into the following: Web Inspector: capture an async stack trace when web content calls addEventListener <https://webkit.org/b/174739> Web Inspector: capture async stack trace when workers/main context posts a message <https://webkit.org/b/167084> Web Inspector: capture async stack trace when web content calls fetch, XHR.send <https://webkit.org/b/174742>
Note You need to log in before you can comment on or make changes to this bug.