Page history

Fitzgen

→‎2. Telling the DevTools Frontend About the New Markers: update based on moved directories

Victor.porof

→‎Using TimelineConsumers

Victor.porof

→‎Using mozilla::AutoTimelineMarker

Victor.porof

→‎Using mozilla::AutoGlobalTimelineMarker

Victor.porof

Update documentation to reflect the new API

Fitzgen

→‎2. Telling the DevTools Frontend About the New Markers: fix path again

Fitzgen

→‎2. Telling the DevTools Frontend About the New Markers: fix path

Fitzgen

→‎2. Telling the DevTools Frontend About the New Markers: add suggested reviewers

Fitzgen

→‎Recording Markers in a Different Thread: link bug for different threads

Fitzgen

What is a good candidate for tracing?

Fitzgen

→‎2. Telling the DevTools Frontend About the New Markers: bold

Fitzgen

→‎2. Telling the DevTools Frontend About the New Markers: describe properties

Fitzgen

more changes

Fitzgen

fix screenshot

Fitzgen

adding intro

Fitzgen

Fitzgen moved page DevTools/PerfMarkers to DevTools/OperationInstrument: Renaming to what we are calling this push.

Fitzgen

structure

Fitzgen

more edits

Fitzgen

→‎Platform: f

Fitzgen

→‎Example Bug: Tracing HTML and XML Parsing: f

Fitzgen

→‎Frontend: g

Fitzgen

→‎Frontend: more stuff

Fitzgen

adding example

Paul

Created page with "== Instrumenting Gecko: adding new markers == The Firefox performance tool breaks Gecko operations into labeled chunks of time, displayed as a waterfall (reflows, painting, r..."