Make 0 == 0 instead of <1, hide user time, make average go from system time.

Right now the pages will stay in a limbo state with a broken content script.

Show the total number of events, duration of the time range, selection information, etc.

A tool that ran over code to generate an instrument.js file from annotations/a regex would be nice. This could prevent the need for any manual wtf.trace.instrumentType calls.

e.g.,

wtf-autoinstrument src/ mytypelist.yaml my.tracing.ENABLED > instrument.js

mytypelist.yaml could contain the types/methods in a readable form and use regexes:

my.Type:
- *
my.OtherType:
- /methods/

The generated code would look like:

if (my.tracing.ENABLED) {
  wtf.trace.instrumentType(...);
  ...
}

??

If an exception is thrown the trace will be broken. Add proper scope depth tracing in wtf.trace to do auto unwinding on unmatched leaves.

Currently the popup UI will not take focus. The window.focus() does not work from the extension. Perhaps steal focus in the window itself? Or use chrome.tabs.create?

Ability to pick extensions and set 'run level' (0=off, >0=verbosity)

The heatmap is largely useless right now. It'd be nice if it was able to fill scope events in, such as GCs, to show time occupied by each event type given instead of just instance occurrences. It'd also be nice to have the relative intensity based on the entire trace, not just the active viewport.

Add a perf test runner (bin/perf-runner.js?) and some perf tests under test/perf/
It'd be nice to know the overhead of scopes/instance events, auto instrumentation via wtf.trace.instrument, etc.

Right now BinaryTraceSource does the work required for tracking Scope depth. This prevents scopes from other sources or out-of-order scopes from nesting properly. Ideally, scope depth tracking is handled by the ZoneIndex that the scope falls inside.

A bug with position: fixed perhaps?

Display a loading message in the UI instead of 'drag files mumble' when loading large files.

All zoom viewport changes should be modifying the DocumentView.localView (wtf.doc.View) and all renderers should be using that to draw themselves.

Hide these from the UI (such as flow events, frame.*, etc).

Instead of using wall time in the event stream use a relative time to some chosen tracelistener shared timebase. This can be set as the first timebase encountered in any file.

Add a 'enable gc/system events' checkbox to the HUD settings.
Add a 'reset to default' button thing.

Build rules to place the app into the injector and default to loading from there.
Add app detection to use that if installed.

wtf.scope.leave is getting dispatched with isCustom - this is wrong.
Time to clean up the dispatchEvent_ methods.

Add a 'user' time duration to scopes and properly handle subtracting gc/compilation/trace time from them. All statistics can show a 'user' value alongside a 'wall' value.

When you click on an item the "mean" button right now appears to give you the mean rounded to the nearest msec. Would be good to make that at least 3 digits of precision so you don't get just "1" or "0" for every item that 's in the vicinity of 0-1 msec.

See what's available via timeline, would be nice to show things like paints, image decodes, etc.

When you zoom in with the mouse wheel it centers the zoom on the mouse position.
When you zoom in/out with W and S keys, it doesn't do that. I think it should.

https://developer.mozilla.org/en-US/docs/Extensions

Especially when zoomed way out (so that a scope is smaller than a pixel) it's hard to find the result. Highlighted results should not be antialiased away.

Doing a Function.toString() and parsing out the arguments would allow for the generated wrapper functions to avoid the use of arguments/apply. This may make things much faster.

This will enable event overlays and such, like easy importing from V8 logs without requiring conversion via scripts.

Make keyboard arrows faster and mouse zoom slower.

Synchronized is hard, so maybe just the tracks panel one.

It should probably only show up when there's a search active.

Support flow tracking across postMessage/onmessage.

Basic support is in.

• track flows on postMessage
• track message size in postMessage/onmessage
• track errors/etc?
• hook event handlers properly in workers

Perhaps a popup on the URL button? Global hotkey? etc?
Maybe a way of adding some UI to the new tab page?

The name should use the msg arg (if present). This can be fixed up by making the wtf.analysis.Scope have a getName function that does this work.

Right now if you enable the extension on a page with the embed settings will be overwritten and things messed up. It'd be nice to prevent the extension from running if the page has the embed - perhaps by either having the embed no-op or reloading and disabling.

With changes for CSS name prefixing. This will allow for GSS to be used in the HUD and the SettingsDialog to be generalized and usable from the app UI.

For the selected time range show all events sorted by total time with call count/min/max/avg time/etc.

chrome.tabs.captureVisibleTab can make JPGs/PNGs. They'll probably need to be rescaled first.

Navigation keys/hidden functionality would be nice to expose like Chrome dev tools does.

Show as broken images in IE10. content: url(svg) not supported? May be best to move to a different mechanism entirely.

The data table values limit to events in the selection time range, however it should find scopes that intersect the time range too like the zone painter does.

Traditional audio editor-like UI. Click/shift-drag, resize, move, etc. Update the current filter or have a selection?

Add a ctrl-M (or something) that lets you pick between markers in the stream to jump to, like ctrl-G.

• Add plumbing to get debugger data from the extension into the injected page.
• Add debugger attaching (maybe a special option?)
• Get GC events from the debugger
• Show GCs in the framebar/etc as special