Nazım Can Altınova

We are removing the old active tab view and creating a new one. It's not relevant with the new one anymore, so closing it.

We don't need this for the active tab view anymore as it won't have merged threads by default. But this is still needed for merged threads overall, so keeping it...

Also :dholbert filed a bug for that in bugzilla here: https://bugzilla.mozilla.org/show_bug.cgi?id=1829955 .

We don't need this for the active tab view anymore as it won't have merged threads by default. But this is still needed for merged threads overall, so keeping it...

Here's a documentation to the profile file format: https://github.com/firefox-devtools/profiler/blob/main/src/types/profile.js and some some more documentation here: https://github.com/firefox-devtools/profiler/tree/main/docs-developer

Hey folks, we had an in-person chat with @mrchrisadams 2 days ago and I was made aware of the issue where browsertime fails when the "power" feature is set to...

@mrchrisadams Oh, I wasn't aware of the `--config` option already. Yes, this config json file makes things a lot easier with the way you use it. For `--browsertime.firefox.geckoProfiler`, I think...

@soulgalore Nice! We use `schema` to identify which data field corresponds to which value. If you look at the line above, you'll see this: ``` schema: { time: 0, count:...

Hm, I'm not so sure about the name. We simply call them "power" in the Firefox Profiler but already having "powerUsage" makes it trickier.

Yes, it should work as expected without the extra wait if we properly await the `Services.profiler.StartProfiler`. Not sure if we are doing it already? [I see an `await`](https://github.com/sitespeedio/browsertime/blob/79e9b0e1f72c3005641b1131173cdaaf24f93a51/lib/firefox/geckoProfiler.js#L89) in front...