Bug 148322 - Web Inspector: Call Stack in Debugger tab navigation sidebar should show native entry points
Summary: Web Inspector: Call Stack in Debugger tab navigation sidebar should show nati...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: WebKit Nightly Build
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2015-08-21 12:32 PDT by BJ Burg
Modified: 2016-12-13 15:41 PST (History)
5 users (show)

See Also:

Attachments
test case. (458 bytes, text/html)
2015-08-21 12:32 PDT, BJ Burg 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description BJ Burg 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.
Comment 1 Radar WebKit Bug Importer 2015-08-21 12:32:43 PDT 
<rdar://problem/22383514>
Comment 2 BJ Burg 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.
Comment 3 BJ Burg 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.