fix(website): keep Page Up and Page Down working in metadata margins - #96
Merged
Merged
Conversation
Release type: patch Previous version: 2.3.8 New version: 2.3.9
Contributor
|
🚀 Release The version bump and changelog have been committed. When this PR is merged, tag |
Lucki2g
approved these changes
Oct 5, 2026
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
2 participants
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.
Clicking the blank margin beside a metadata table could stop Page Up/Page Down from scrolling. The margins now belong to the scrollable region, which is also reachable with Tab. Table widths and spacing stay the same.
Before — click the margin and press Page Down: the page stays put
After — the same action scrolls down to the next table
Validated with synthetic sample data: Page Up/Page Down, both margins, keyboard-only navigation and search-field focus at 1280–1920px widths. Website lint and full production build passed on Node 22.23.2 with existing warnings.