- π³π±Netherlands johnv
I guess this can be postponed until the older, more generic and more active issue [31210980] has landed.
Ff you have several pages of content with a few dozen nodes per page on for example /admin/content
the user has to scroll down the whole page (see
long_list.png β
) to reach the pager component which happens to be only available at the bottom of the list. In particular on mobile devices the user has to scroll all the way down to being able to deliberately navigate to any page without having to rely onto the browsers back and forward functionality.
Background: In the usability meeting #3304790: Drupal Usability Meeting 2022-08-26 β we've discussed π Reset button shows on exposed filter defaults Closed: outdated (attendees were: @AaronMcHale, @DyanneNova, @shaal, @simohell and me). During the discussion we've agreed the reset button should only function in the context of the filter functionality (see #44 π Reset button shows on exposed filter defaults Closed: outdated . But we also acknowledged the general usefulness of the hidden "back button" functionality. So we agreed to open a followup issue to keep the initial issue in scope.
- create 300 or 400 content nodes with Devel
- go to /admin/content
- try to navigate the pages without relying on the browsers back and forward functionality.
you currently have the Apply to selected items
button on top and at the bottom of the list but the pager component in contrast is only available at the bottom of the list. It would be consistent as well as helpful to add the pager also on top of the list. so you have the button and the pager on top as well as at the bottom of the list.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I guess this can be postponed until the older, more generic and more active issue [31210980] has landed.