pagination info at top and bottom of any horizon table

Bug #1359238 reported by David Medberry
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Low
Revon Mathews

Bug Description

Hello dear OpenStack dashboard folk:

Pagination info at top and bottom of any horizon table. For instance, by default, you typically limit table size to 20 but only display that there are more than 20 returned entities at the bottom of a page. GOOD UX DESIGN PRINCIPLES REQUIRE THAT YOU DISPLAY THIS AT TOP AND BOTTOM OF A PAGE. And that you be able to go to the next "n" entries from the top or bottom via a navigator button.

*(Yes, I yelled.)*

Tags: ux
Revision history for this message
Liz Blanchard (lblanchard) wrote :

Hi David,

Thanks for the passionate statements about the pagination design in horizon. I think there are a lot of UX improvements that need to be made to pagination, including this one.

You will notice a range of pagination features depending on which set of data you are looking at. There are a number of bugs reported on this. Here is one that includes the fact that the "More" button should really be "Next". It also refers to a bug around needing to allow users to select how many items per page the table is showing within the table itself:
https://bugs.launchpad.net/horizon/+bug/1212174

I think this addition would ease the pain a bit of scrolling a number of items and then having to scroll all the way back up the list for pagination, but it does not solve this issue.

Best,
Liz

tags: added: ux
Changed in horizon:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Raghuram Gundimeda (raghuram-gundimeda) wrote :

On a slightly different note, pagination (in my opinion) is not necessarily an answer for data tables, always. While it might add to the overhead of code and its maintenance, it definitely adds (avoidable) intellectual and motor load on the user (deciding, customizing, traversing back / forth in trying to reach his target row, accompanying errors while doing so, etc).

Excuse my ignorance, for I am not fully aware of all table traversal features that we currently have in Horizon, but we can definitely go for something that saves on issues I just stated - say, as a fixed header table with scrollable but fixed height, that lazy-loads data (fetch rows on demand) as the user scrolls down. We can do away with pagination and customization + their overheads altogether.

Just some thoughts...

Changed in horizon:
assignee: nobody → tcs_openstack_group (tcs-openstack-group)
Changed in horizon:
assignee: tcs_openstack_group (tcs-openstack-group) → nobody
Changed in horizon:
assignee: nobody → jelly (coding1314)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

Fix proposed to branch: master
Review: https://review.openstack.org/182532

Changed in horizon:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: master
Review: https://review.openstack.org/183962

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on horizon (master)

Change abandoned by Kuo-tung Kao (<email address hidden>) on branch: master
Review: https://review.openstack.org/183962
Reason: The test code should not commit by oneself.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

Fix proposed to branch: master
Review: https://review.openstack.org/183963

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on horizon (master)

Change abandoned by Kuo-tung Kao (<email address hidden>) on branch: master
Review: https://review.openstack.org/182532
Reason: It is redundant now.
The new version is https://review.openstack.org/#/c/183963/ .

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Change abandoned by Kuo-tung Kao (<email address hidden>) on branch: master
Review: https://review.openstack.org/183963
Reason: Wrong patch.

Changed in horizon:
assignee: jelly (coding1314) → nobody
status: In Progress → Confirmed
Changed in horizon:
assignee: nobody → Revon Mathews (revon-mathews)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

Fix proposed to branch: master
Review: https://review.openstack.org/356667

Changed in horizon:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.openstack.org/356667
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=b65b476a1b85179af46385a910c9a2beba33cd45
Submitter: Jenkins
Branch: master

commit b65b476a1b85179af46385a910c9a2beba33cd45
Author: Revon Mathews <email address hidden>
Date: Wed Aug 17 13:51:24 2016 -0500

    Added the pagination info at top of the table

    Added a reusable pagination template that is now applied to the top
    and bottom of the data_table.

    Change-Id: I7eb040b9c08fef984d20c8dba560cfe0c8be8cac
    Closes-bug:#1359238

Changed in horizon:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to horizon (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/376066

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to horizon (master)

Reviewed: https://review.openstack.org/376066
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=b94f060b343133835283f6debc4d124bbfd95666
Submitter: Jenkins
Branch: master

commit b94f060b343133835283f6debc4d124bbfd95666
Author: Kenji Ishii <email address hidden>
Date: Mon Sep 26 10:28:28 2016 +0900

    A following up patch for 'Added the pagination info at top of the table'

    Originally, 'Displaying x items' is included in footer area.
    However, the element that the previous patch added is not in this area.
    Thus, when the number of rows in table is zero, this behaviour is difference
    (the element at the bottom of the table is hide, but the element
    at the top of the table remain displaying).
    I think these should be same behaviour as a footer information.

    Change-Id: I6eb10db2bf00c8686c0df9d990787a2a890e6340
    Related-Bug: #1359238

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/horizon 11.0.0.0b1

This issue was fixed in the openstack/horizon 11.0.0.0b1 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.