Skip to content
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

Fix check for menu cannot fit on top #5743

Merged
merged 1 commit into from
Apr 26, 2024

Conversation

JingkangZhang
Copy link
Contributor

@JingkangZhang JingkangZhang commented Mar 20, 2024

issue #5740

Originally, the check doesn't consider the resolution height, but the resolution height is being used below to determine the style.top. This causes the element to overlap with the parent box, and in turn causes the menu to close onScroll, because of the check here.

Screenshot 2024-03-20 at 3 14 23 AM Screenshot 2024-03-20 at 3 31 46 AM

Add the height check to the RHS of the > , so the menu won't be placed on the top if it cannot fit.

Taking a step back, I'm not sure why when the menu is placed on top of the cursor, it's height length away from the cursor, whereas when the menu is placed below the cursor, it's 0 length away from the cursor. In other words, we could have removed both + height on line 519 and - height on line 522, but I didn't implement that to preserve the original style.

Results

Before:
Screenshot 2024-03-20 at 4 33 28 AM

After:
Screenshot 2024-03-20 at 4 33 46 AM

Copy link

vercel bot commented Mar 20, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
lexical ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 20, 2024 11:37am
lexical-playground ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 20, 2024 11:37am

@facebook-github-bot
Copy link
Contributor

Hi @JingkangZhang!

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!

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Mar 20, 2024
Copy link
Contributor

@StyleT StyleT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks for contribution

@StyleT StyleT merged commit 988a25a into facebook:main Apr 26, 2024
45 checks passed
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 Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants