mgr/dashboard: Global/independent actions should not depend on row selection in a table
Currently, user has to select a row in a table in order to perform an Add/Create action. Global/independent actions should not require row selection if not needed and should be de-coupled.
Pattenfly approach for row specific/table specific actions: https://www.patternfly.org/pattern-library/content-views/table-view/#code, https://pf4.patternfly.org/components/Table/examples/
#1 Updated by Ju Lim about 1 year ago
This was mentioned and discussed here https://pad.ceph.com/p/dashboard-f2f-2019-general-best-practices.