Bug 148322

Summary: Web Inspector: Call Stack in Debugger tab navigation sidebar should show native entry points
Product: WebKit Reporter: Blaze Burg <bburg>
Component: Web InspectorAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: graouts, inspector-bugzilla-changes, saam, webkit-bug-importer, ysuzuki
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: All   
OS: All   
Attachments:
Description Flags
test case. none

Blaze Burg
Reported 2015-08-21 12:32:12 PDT
Created attachment 259642 [details] test case. We usually display native functions as (anonymous functions) even when we know exactly what they are. We should do better. In the attached test case, one of the anonymous frames is actually EventTarget.dispatchEvent.
Attachments
test case. (458 bytes, text/html)
2015-08-21 12:32 PDT, Blaze Burg 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2015-08-21 12:32:43 PDT
<rdar://problem/22383514>
Blaze Burg
Comment 2 2016-06-03 12:37:33 PDT
Now we don't even see who dispatched the event. I don't know if this is a regression, but it does not show on Safari 9.1. Retitling.
Blaze Burg
Comment 3 2016-06-03 12:40:44 PDT
In the case of this test case, I would expect the bottom call frame to be something like "Dispatched DOM Event". Clicking on the call frame wouldn't do anything since there is no source location. There are many other entry points, such as requestAnimationFrame, timers.
Note You need to log in before you can comment on or make changes to this bug.