Add Duration/Size columns to the header of view-event list.

[Haoxiqiang]

The request list shows the duration/size may be more intuitive for analysis.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[pimterry]

Hi @Haoxiqiang, thanks for this! Great move 👍 👍 👍

In general I'm totally on board with this as a feature, it makes perfect sense, but I know some users already have issues with the limited UI space in the view list, and this would make that worse.

I think this would be fine if it was optional though. Would you be up for adding that? I'm imagining a little ... button in the top right of the headers, where you can toggle columns on & off. I would suggest only including these two new columns in the options there, not the existing ones for now, as toggling the built-in columns may be quite a bit more complicated (due to some new rows with non-matching layouts - see EventTypeColumn, RTCEventLabel, BuiltInApiRequestDetails etc).

Does that make sense?

[pimterry]

I think this whole chunk would probably be nicer as a reusable function like formatDuration somewhere, e.g. src/util/index.ts.

[Haoxiqiang]

ok, I'll do it later.

[Haoxiqiang]

Refactored the code.

Most of the time, the space is actually enough, even if it is not enough, the path part can be compressed.
A button on the right side of this may not be pretty, I'll think about how to do it.

[pimterry]

Great, thanks for refactoring that 👍.

A button on the right side of this may not be pretty, I'll think about how to do it.

To be clear, I'm imagining something like this:

When clicking those dots, it can just open a little menu beneath with checkboxes, something like:

Show extra columns:

[ ] Duration
[ ] Response body size

I'm sure you're right that on a normal screen it fits fine in most cases, but there's definitely lots of users with much smaller screens, and at 1024x768 it's already all pretty squeezed!