Skip to content

Implement anchored ContextMenu positioning and update documentation#3473

Open
akoweicollinxx wants to merge 1 commit into
facebook:mainfrom
akoweicollinxx:fix/contextmenu-anchor-positioning
Open

Implement anchored ContextMenu positioning and update documentation#3473
akoweicollinxx wants to merge 1 commit into
facebook:mainfrom
akoweicollinxx:fix/contextmenu-anchor-positioning

Conversation

@akoweicollinxx

Copy link
Copy Markdown

This PR updates ContextMenu to use anchored/context positioning instead of fixed cursor coordinates.

The menu is now anchored to the trigger element, which means it:

scroll-follows its target instead of detaching when the page moves
can auto-flip/shift near viewport edges via the anchored layer behavior
preserves the existing focus restoration and Escape-dismiss behavior
What changed
switched ContextMenu from useLayer({ mode: 'fixed' }) to useLayer({ mode: 'context' })
removed fixed x/y positioning from the menu render path
kept right-click open behavior, focus restore, and keyboard navigation intact
Updated ContextMenu docs to describe anchored behavior
Updated tests to match the new anchoring model
Notes
This is a follow-up to the earlier invocation work that intentionally kept fixed positioning. It completes the anchoring follow-up tracked in #3465.

Testing
Updated unit tests for ContextMenu behavior
verified open/close, Escape handling, and focus restoration still pass

@vercel

vercel Bot commented Jul 2, 2026

Copy link
Copy Markdown

@akoweicollinxx is attempting to deploy a commit to the Meta Open Source Team on Vercel.

A member of the Team first needs to authorize it.

@meta-cla

meta-cla Bot commented Jul 2, 2026

Copy link
Copy Markdown

Hi @akoweicollinxx!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@meta-cla

meta-cla Bot commented Jul 2, 2026

Copy link
Copy Markdown

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Meta Open Source bot. label Jul 2, 2026
@meta-cla

meta-cla Bot commented Jul 2, 2026

Copy link
Copy Markdown

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Meta Open Source bot.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant