[BUG FIX] [MER-5107] Reposition Support and Cookies on Adaptive Page Not Fullscreen - Rework#6563
Draft
gastonabella wants to merge 1 commit intomasterfrom
Conversation
…es content and nav footer.
Contributor
Contributor
AI Review — securityNo issues found |
Contributor
AI Review — performanceNo issues found |
Contributor
AI Review — elixirNo issues found |
Contributor
AI Review — uiNo issues found |
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.
MER-5107
Reworks the original MER-5107 fix to address the overlap issue reported on adaptive pages. On smaller screens, the Support and Cookie Preferences controls were overlapping adaptive content, CC attributions, and previous/next navigation instead of sitting in the intended footer area.
This update makes the adaptive-page controls footer-bound rather than viewport-fixed, so they no longer float over page content while scrolling. It also keeps the responsive behavior separated between adaptive and non-adaptive pages, preserving the existing non-adaptive layout while applying adaptive-specific spacing and mobile visibility rules.