Fix/prev next layout#5279
Open
abhijeetnardele24-hash wants to merge 1 commit into
Open
Conversation
abhijeetnardele24-hash
force-pushed
the
fix/prev-next-layout
branch
from
63fec9b to
a225472
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR refactors the footer CSS to ensure the "Previous page" and "Next page" navigation links remain side-by-side on narrower viewports.
Currently, the two-column grid layout for
.prev-nextrelies on a@media (min-width: 640px)query, causing the links to unnecessarily stack vertically on mobile screens, which consumes excess vertical space and looks bulky. This PR removes that media query and applies the two-column grid unconditionally, matching the layout expectation described in the issue.Linked Issues
Resolves #5208
Additional Context
Tested against mobile viewports down to 320px width to ensure the side-by-side buttons do not overflow or overlap the container boundaries.
Tip
The author can publish a preview release by commenting
/publishafter creating the PR.