[Users Table]: Reconsider header:table height ratio #13699
Description
❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.
Overview
@tomiwaoLE @marcellamaki and @nucleogenesis to review the height and header spacing on the user tables in Facility to develop a consistent design that optimizes table visibility while maintaining clarity in the header's information and actions.
UX Bash Notes
I know we had some extensive discussions about the table height but in terms of the ratio of page space (less about whether or not it was the right “meta” choice for KTable) it feels like there is too much space for non-KTable stuff.
almost equal space being given to the header (which on the new users table is honestly a lot of empty space) as there is to table rows.
not so much a critique of the table being all in view so we can see the pagination (which seems good) but more looking at the page as a whole
- i think the rows should be narrower
- i think we should think about redistributing the headers space
I guess the other thing here is by constraining the height so that the header is always in view, there is no scenario by which a user could scroll down and see the entirety of the table, whereas before (when the scroll was in the page, not in the table), that was possible. I’m not saying that’s ncessarily better, just thinking through more tradeoffs that i hadn’t considered before. almost wonder if we just made the bottom pagination bar sticky (this is probably more complicated than I am imagining) but still had the scroll live in the page, not in the component