[BUG][UI]: Experiment view table nits

[rickarize]

Couple things:

1. "avg" vs "AVG" in the aggregate metrics header – we should probably have a formalized component for value display that includes an isAverage prop (and isPending etc) or something, because we use these everywhere and want consistent formatting, spacing between values and the surrounding elements, etc.
2. Table with small number of rows should take up remaining page height so the horizontal scrollbar is at the bottom of the window and not in the middle
3. Tokens, latency, cost, etc should hug their content more and make room for the output. Yasmine had some good context about this: this is for headroom for future anomalous values. The table content is virtualized/paginated and we don't know all values that will enter in the future, so we provide headroom for extreme things in the future. We can still adjust these defaults and the way values truncate to get improved spacing.

[dosubot]

Great suggestions—these UI nits have come up in related threads. There’s no evidence of a formalized value display component with props like isAverage or isPending yet, but your idea would help standardize formatting and spacing for aggregate metrics, which has been a recurring theme in issues about experiment compare table headers and metric display consistency (#8752, #8760).

For the table height and scrollbar, similar layout bugs have been reported where tables don’t fill the available space or scrollbars appear mid-page, often due to CSS or container constraints (#9979, #9825). Reviewing the table’s parent container and ensuring it uses flex or grid to fill vertical space should help keep the scrollbar at the bottom.

Standardizing value display via a shared component and auditing table layout logic for full-height rendering would address both issues and align with ongoing UI consistency efforts.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}