Adopt row virtualization for any table over 500 rows
Make windowing the default pattern for large tables across the console.
Runs table freezes the tab at ~3,000 rows — make it stay smooth
Design partners report the runs tab pins the CPU with thousands of rows. Keep it interactive without a heavyweight dependency if possible.
Slack · #eng-web · thread ↗Ready for your review
Two viable approaches both compiled and kept the table working; there's no behavioral test that captures 'feels smooth', so the fleet couldn't pick on its own. An independent reviewer suggested Worker B (a dependency-free window) over Worker A (adds a virtualization library). Your call.
Load the Runs tab with 3,000 rows → Scroll top-to-bottom fast → No freeze — only visible rows are mounted
npm run build && npm test -- RunsTableReported by two design-partners on the runs view.
Make windowing the default pattern for large tables across the console.