Florian Quèze

https://phabricator.services.mozilla.com/D151127 will hide the issue again by removing the primary source of long markers starting before the profiler.

Another example profile where this was very visible recently: https://share.firefox.dev/3IEvkhl

> * Hide the "Call Tree", "Flame Graph" and "Stack Chart" panels by default. This would match the behavior we have with the "Network" panel that is only visible when...

The 2 use cases I had for wanting to select marker names were: - using the findbar to find a marker quickly. This is case is indeed well covered by...

> > selecting a marker name to search it in searchfox to figure out which code generates it. > > Is this something the sidebar would solve? Hopefully it will,...

I kinda like the times there, especially because this lets the Flame graph show values that match the Stack chart. But I understand your concern. I wonder if it would...

In https://phabricator.services.mozilla.com/D151128 I'm changing these counters' name to something that includes the word 'power', so this issue might be less of a problem, but probably still worth fixing anyway.

The vertical alignment between the blue or grey bars and the text looks like it could be improved. I think it would look better if the bottom of the colored...

I just tried the deploy preview (https://deploy-preview-4243--perf-html.netlify.app/public/n6vyjpmv615vhf7zrhy6rbczvenqb4nj2zjf1mg/marker-chart/?globalTrackOrder=ab0w9&hiddenGlobalTracks=1wb&hiddenLocalTracksByPid=11073-0wa~11082-0w2~11074-0w2~11080-0w2~11084-0w2~11083-0w2&range=7958m1320&thread=0&v=7). This is exciting! I find that the strings are pretty long and make the tooltip harder to read. How would you feel about...

> How do we go about updating the strings to represent this? I think @julienw can help you with the next steps.