135746 2014-08-07 22:28:46 -0700 Web Inspector: add a Scripts timeline record for Promise fulfillment 2016-07-22 20:05:08 -0700 1 1 1 Unclassified WebKit Web Inspector 528+ (Nightly build) All All RESOLVED FIXED InRadar P2 Normal --- 1 burg webkit-unassigned barraclough graouts joepeck sam timothy webkit-bug-importer oldest_to_newest 1027780 0 burg 2014-08-07 22:28:46 -0700 This will require new instrumentation. It should be like Timer Fired, except more promising. It should be simple to also include whether the promise was resolved or rejected. Sometimes, it doesn't quite work the way people expect.. :) 1027781 1 webkit-bug-importer 2014-08-07 22:29:23 -0700 <rdar://problem/17956025> 1028045 2 burg 2014-08-08 23:24:17 -0700 I am not sure how we would get these callbacks through to an inspector agent. Current paths include plumbing to call into the global object's JSGlobalObjectInspectorController (i.e, to report exceptions) and through ScriptDebugServer listeners. The former seems better here, but that controller is guarded by ENABLE(REMOTE_INSPECTOR). Any thoughts, Joe? 1028237 3 joepeck 2014-08-11 11:29:12 -0700 (In reply to comment #2) > I am not sure how we would get these callbacks through to an inspector agent. Current paths include plumbing to call into the global object's JSGlobalObjectInspectorController (i.e, to report exceptions) and through ScriptDebugServer listeners. The former seems better here, but that controller is guarded by ENABLE(REMOTE_INSPECTOR). JSGlobalObjectInspectorController is only for JSContext inspection. I think this should go through the JSGlobalObject::debugger JSC::Debugger (ScriptDebugServer). 1213820 4 joepeck 2016-07-22 20:05:08 -0700 We did this with ScriptProfiler's Event records. Promise fulfillment is a Microtask event, and we have bubbles and profiling data for these evaluations.