#536 documentation Mobile Navigation : Responsive Design#542
Merged
Conversation
|
@A5cend-dev Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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.
Description
Fixed the mobile navigation responsive behavior by updating
MobileNavigation.tsx.The navigation now remains a bottom tab bar for compact and portrait mobile screens, while switching to a left-side rail only on screens with a minimum width of 640px in landscape orientation. Safe-area inset handling was preserved to improve usability across devices, and the component was marked as a client component to properly support hook usage in Next.js.
Type of Change
Bug fix focused on improving responsive behavior and mobile user experience without affecting existing functionality.
Notes
The update follows project coding standards, maintains accessibility considerations, and introduces no known console errors or regressions.
Closes #536