Common UX pattern from spreadsheets, IDE editors, and most data-grid components: double-clicking the column resize handle auto-sizes the column to fit its widest visible content.
Proposed behavior: double-click the resize handle on any column header → measure the widest text in the visible portion of that column (header + visible rows) and set the column width to fit, with reasonable padding.
Implementation notes:
- Iterate visible
.log-row .{class-for-col} elements, take scrollWidth (or measure via canvas), use the max
- Cap at some sensible max (e.g., 50% of viewport) to prevent runaway widths
- For "Module" specifically, this would solve the "long Bluetooth-stack module name" problem in one click
Common UX pattern from spreadsheets, IDE editors, and most data-grid components: double-clicking the column resize handle auto-sizes the column to fit its widest visible content.
Proposed behavior: double-click the resize handle on any column header → measure the widest text in the visible portion of that column (header + visible rows) and set the column width to fit, with reasonable padding.
Implementation notes:
.log-row .{class-for-col}elements, takescrollWidth(or measure via canvas), use the max