Scenario: there is
an intranet application; for its admin interface where the admin will
view the user list which can be long enough. Each row displays the
details for a user.
There will be actions like "Add new user",
"Edit user" and "Delete user"; as the last two action can be performed
on any of the rows. Instead of giving links for Edit and Delete along with each row, action buttons are given at the top and bottom of the list.
suggestion on the point that is there any guideline of usability which
says that when you give global action buttons, the height of the
list/table should be fixed; so that the buttons are displayed always? And to view more in the list either there is a scroll within the list or pagination.
if the list is long you can do pagination for e.g.; 20 user rows on
each page and the action buttons can be given both at the top and the
bottom of the list to reduce the motor load.
Another point here is regarding freezing the header in long lists: That
incase if the list has data like pure numbers; then freezing the header
part should be done so that one can makes sense of the numbers as in
they belong to which category by seeing the heading.
But if the
data is like name, email id, role, contact number; then it does not
require the header to be displayed always while you are scrolling as
the data itself is explicit enough.