-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Fix sidebar layout shift on Sistent page refresh #7938
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
Open
Katotodan
wants to merge
2
commits into
layer5io:master
Choose a base branch
from
Katotodan:fix/sitent-component-pg-layout
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+8
−3
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Reset the minimum width in the mobile layout.
TOCWrapperalready haswidth: 15remon Line 9, so this rule does not add a desktop width reservation. Themax-width: 750pxmedia query changeswidthtoautobut leavesmin-width: 15remactive. On narrow viewports, this can cause horizontal overflow together withmargin-right: 3rem.Add
min-width: 0in the mobile media query, or scope this rule to the desktop layout.As per coding guidelines, the component must maintain responsive mobile-first behavior.
Proposed fix
`@media` only screen and (max-width: 750px) { position: initial; margin-right: 3rem; width: auto; + min-width: 0; }🤖 Prompt for AI Agents
Source: Coding guidelines
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have tested this on small devices, and everything was working correctly. The size set for small devices was superior to 15rem already so that prevents it from even shrinking in any unknown senario.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Katotodan, the tested devices validate the current layout at those viewport sizes.The concern is limited to a narrower available content width. In the mobile media query,
width: autodoes not overridemin-width: 15rem. The wrapper can therefore not shrink below15rem, regardless of the available width after margins.If the supported mobile viewport and container widths always exceed that limit, the current rule is safe. Otherwise, reset
min-widthin the mobile media query to preserve the intendedwidth: autobehavior.(ᵕ•_•) 🐇
You are interacting with an AI system.