Feature Proposal: Configurable Row Display Limit for Table Panels

[MikaelEngvall]

Problem

Table panels display a maximum of ~10 visible rows regardless of panel height or query limit settings. When a table has 25 rows of data but the panel is tall enough to show all of them, users still have to scroll through an internal scrollbar.

This is especially problematic for overview dashboards where you want a full list of services, endpoints, or resources visible at a glance — without requiring interaction.

Current behavior

• Panel is tall (e.g., 600px), query returns 25 rows
• Table renders ~10 rows and adds an internal scrollbar
• The rest of the panel height is wasted as empty space below the table

Desired behavior

• Table fills the available panel height, showing as many rows as fit
• Or: user can configure a specific number of visible rows (e.g., 25, 50, or "all")

Proposed Solution

Add a visibleRows configuration option to the table widget settings:

{
  "visibleRows": "auto"  // fill panel height
}

Or with an explicit count:

{
  "visibleRows": 25
}

Options:

• "auto" (default for new panels) — calculate row count from panel height
• A number (e.g., 25) — show exactly that many rows, scroll if more exist
• 10 — current behavior, for backward compatibility

UI approach:

• In table panel settings, add a "Visible Rows" dropdown or input field
• Options: "Auto (fill panel)", or a numeric value
• Default remains 10 for existing panels (backward compatible)

Technical Scope

• Frontend only — no backend changes required
• The table renderer currently appears to hardcode a row count or fixed height for the virtualized list
• Change it to derive visible row count from the panel's available height (minus header/padding)
• Accept an optional visibleRows field from widget config
• Backward compatible: panels without visibleRows keep current behavior

Willingness to Contribute

I'm happy to implement this and submit a PR. I'd appreciate knowing:

• Whether the table uses a virtualized renderer (react-window, react-virtualized, or similar)
• If there are performance concerns with rendering 50+ rows without virtualization