Repository navigation
refactor: remove disabled tooltip from PaginationNavButton - #21199
Merged
Merged
Conversation
aslilac
approved these changes
Dec 11, 2025
aqandrew
deleted the
aqandrew/replace-mui-tooltip-paginationnavbutton
branch
December 11, 2025 18:43
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
for #19974
The MUI tooltip inside
PaginationNavButtonwas a controlled component. This + the stateful logic insidePaginationNavButtonCoremeant thatshowDisabledMessagewould never be set to true. I.e., the "You are already on the first page" tooltip if on the first page and the "You are already on the last page" tooltip if on the last page would never show up.The
PaginationNavButtons gets disabled if we're at either the first/last page, and disabled buttons can't receive focus, so there's no way to open the MUI tooltips with keyboard navigation.Removing the MUI tooltip + related props from
PaginationNavButtonhas no effect on my screen reader UX with macOS VoiceOver; it's entirely unchanged