1868805 - [meta] Add a "moz:profiler" module for recording Firefox profiles

Status: NEW

(Remote Protocol :: WebDriver BiDi, enhancement, P3)

Description

[Nazım Can Altınova [:canova][:canaltinova on phabricator]]

After talking with Henrik, I learned that it's pretty straightforward to add a new module to WebDriver BiDi. Currently WebDriver BiDi specification doesn't have anything for tracing/profiling. But we can still experiment with adding some "moz:" vendor specific messages.

One thing is that, currently our implementation doesn't support any vendor prefixes for methods. We should support this first.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+1]]

If it's fine with you I would make that a meta bug given that we might need multiple bugs for it.

Also should we move it to the Remote Agent component or leave it here?

Comment 2

[Nazım Can Altınova [:canova][:canaltinova on phabricator]]

I wasn't sure where to file this initially but yeah, I think Remote Protocol component makes more sense. Moving there.

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+1]]

As discussed we could add a moz:tracing module to allow starting and stopping the recording of a Firefox profile. At the beginning it's probably fine to not stream the recorded profile but just save it to disk based on a file name as given to the start or maybe even the stop method.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+1]]

As commented by Julien over on bug 1868828 the actual API in CDP for the profiler is https://chromedevtools.github.io/devtools-protocol/tot/Profiler/. So we probably should align to it.