Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Query Pagination: Control the layout when next/previous buttons are not displayed #34997

Closed
scruffian opened this issue Sep 21, 2021 · 0 comments · Fixed by #42764
Closed

Query Pagination: Control the layout when next/previous buttons are not displayed #34997

scruffian opened this issue Sep 21, 2021 · 0 comments · Fixed by #42764
Assignees
Labels
[Block] Query Pagination Affects the Query Pagination Block - used for pagination within the Query Loop Block [Feature] Blocks Overall functionality of blocks [Status] In Progress Tracking issues with work in progress

Comments

@scruffian
Copy link
Contributor

What problem does this address?

The new layout controls in the query pagination block give us the ability to align the next/previous buttons, which is super helpful, but when there are fewer posts on a blog, these next/previous links aren't output which means the page numbers can jump around a bit, for example:

Screenshot 2021-09-21 at 11 07 19

Screenshot 2021-09-21 at 11 07 12

What is your proposed solution?

In Blockbase we use CSS Grids to control the position of these elements, which means if one is missing then they continue to stay in the same place.

In addition it would also be useful to have an option to hide page numbers on smaller screen sizes.

@scruffian scruffian added [Feature] Blocks Overall functionality of blocks [Block] Query Pagination Affects the Query Pagination Block - used for pagination within the Query Loop Block labels Sep 21, 2021
@github-actions github-actions bot added the [Status] In Progress Tracking issues with work in progress label Oct 7, 2021
@MaggieCabrera MaggieCabrera removed their assignment Jan 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment