Allow configurable always-visible row actions in EuiBasicTable #9272
Replies: 2 comments
-
|
This is an interesting one. I think feature discover is a constant struggle and balance.
My initial concern is setting us up to make more tables busy. You mention that we already override this in a few areas, so I'm wondering if this needs to be built into EUI? The table options you show in the discussion: isn't the name of the deployment / project be the link to open it? So could we remove this as one of the exposed row actions? All that said, it also seems like what we're asking for is the option for 3 Maybe we tweak how the current props act? Playing around with the example, doesn't seem like If we have |
Beta Was this translation helpful? Give feedback.
-
Given we've been using it in some places, I'm proposing we add it as opt-in configuration (not default). I agree we need to be careful about making tables busy, but in some situations it improves usability. I suggest to allow for:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
I want to propose adding a configuration option to
EuiBasicTablethat allows row text actions to be always visible (not just on hover), with overflow actions in a menu.Proposal
Enhance EUI's
EuiBasicTableto better support always-visible row text actions as configurable behavior. While EUI already providesisPrimaryandshowOnHoverprops, the current implementation has usability limitations that require teams to implement workarounds.The trade-off is between visual density (cleaner tables) and discoverability (users know what's available). The optimal solution is configurability.
What I'm NOT asking
What I am asking
Impact
Configurability should not have any impact downstream. If we keep the default option as-is, other tables will not be impacted.
Background
See conversation in the #eui channel for context. When having more than 2 (text only) actions:
Current behavior
Requested behavior
Use Case (1): Budgets table (user console) - new feature
Our goal: Make important actions immediately discoverable so users don't have to guess what they can do with each row.

Use case (2): Homepage tables
note: this is in the product
OpenandManageactions always visibleUse case (2): Deployments table
note: this is in the product

Additional notes
It's worth noting that custom implementations (see use cases above) result in a modified responsive rendering of the actions menu on mobile breakpoints
Beta Was this translation helpful? Give feedback.
All reactions