fix(docs): correct mobile copy page menu positioning#976
Merged
Conversation
|
@d1rshan is attempting to deploy a commit to the product-studio Team on Vercel. A member of the Team first needs to authorize it. |
Yeom-JinHo
approved these changes
May 29, 2026
Yeom-JinHo
left a comment
Member
There was a problem hiding this comment.
@d1rshan
Tysm for your contribution.
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
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
Fix the mobile
Copy Pagemenu positioning on docs pages.This removes the custom empty
PopoverAnchorfromDocsCopyPageand keeps the mobile menuon the standard Radix trigger/content path so the popover is positioned relative to the
actual trigger button.
Changes
PopoverAnchorfromDocsCopyPagePopoverTrigger+PopoverContentpatternalign="end"DropdownMenubehavior unchangedMotivation
On mobile, the
Copy Pageaction menu could render in the wrong position because thecomponent defined a custom popover anchor without anchoring it to a real element.
Removing that anchor fixes the positioning issue at the source while keeping the
implementation aligned with how other Radix menus are structured in the codebase.
Breaking Changes
None.
Screenshots