Skip to main content
Commonmark migration
Source Link

###Try not to make the user recalibrate their eye position on each pagination action, especially if just the table is refreshing while other page elements remain static.

Try not to make the user recalibrate their eye position on each pagination action, especially if just the table is refreshing while other page elements remain static.

If a table either:

  • loads more on scroll

  • paginates, but refreshes quickly (independent of the other page elements)

The user is going to be thrown off when scanning the columns. Because they scan a table oftentimes like a list, changing the positioning of the columns will force their eye to recalibrate. This is especially true if the table is paginating, but the whole page does not have to refresh.

You could allow manipulation of the column width manually, and talk to your devs if that state can hold across pagination actions on the table.

###Try not to make the user recalibrate their eye position on each pagination action, especially if just the table is refreshing while other page elements remain static.

If a table either:

  • loads more on scroll

  • paginates, but refreshes quickly (independent of the other page elements)

The user is going to be thrown off when scanning the columns. Because they scan a table oftentimes like a list, changing the positioning of the columns will force their eye to recalibrate. This is especially true if the table is paginating, but the whole page does not have to refresh.

You could allow manipulation of the column width manually, and talk to your devs if that state can hold across pagination actions on the table.

Try not to make the user recalibrate their eye position on each pagination action, especially if just the table is refreshing while other page elements remain static.

If a table either:

  • loads more on scroll

  • paginates, but refreshes quickly (independent of the other page elements)

The user is going to be thrown off when scanning the columns. Because they scan a table oftentimes like a list, changing the positioning of the columns will force their eye to recalibrate. This is especially true if the table is paginating, but the whole page does not have to refresh.

You could allow manipulation of the column width manually, and talk to your devs if that state can hold across pagination actions on the table.

Source Link
Mike M
  • 25k
  • 1
  • 58
  • 66

###Try not to make the user recalibrate their eye position on each pagination action, especially if just the table is refreshing while other page elements remain static.

If a table either:

  • loads more on scroll

  • paginates, but refreshes quickly (independent of the other page elements)

The user is going to be thrown off when scanning the columns. Because they scan a table oftentimes like a list, changing the positioning of the columns will force their eye to recalibrate. This is especially true if the table is paginating, but the whole page does not have to refresh.

You could allow manipulation of the column width manually, and talk to your devs if that state can hold across pagination actions on the table.