1870710 - Allow starting the tracer only on next user interaction

Status: RESOLVED FIXED

(DevTools :: Debugger, enhancement)

Description

[Alexandre Poirot [:ochameau]]

One challenge with the JavaScript tracer is the overload of traces being logged.
It is quite frequent that either setInterval/postMessage/mouseover code are polluting the output between the start of the record and the particular user interaction we are trying to debug.
Being able to trigger the tracer only when a user interaction start should drastically help debugging these scenarios.

Comment 1

[Alexandre Poirot [:ochameau]]

Attachment: Bug 1870710 - [devtools] Optionally trigger the tracer only on next mousedown or keydown.

Comment 2

[Alexandre Poirot [:ochameau]]

Attachment: Bug 1870710 - [devtools] Fix rendering of tracer output config.

This was meant to display which one of the two output method was used.

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/3762795af98d
[devtools] Optionally trigger the tracer only on next mousedown or keydown. r=devtools-reviewers,fluent-reviewers,flod,nchevobbe
https://hg.mozilla.org/integration/autoland/rev/c1c3447b8916
[devtools] Fix rendering of tracer output config. r=devtools-reviewers,nchevobbe

Comment 4

[Serban Stanca [:SerbanS]]

https://hg.mozilla.org/mozilla-central/rev/3762795af98d
https://hg.mozilla.org/mozilla-central/rev/c1c3447b8916