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

Incorrect TableActionMenu placement when table is at the bottom of a longer page #10626

Closed
rilrom opened this issue Jan 17, 2025 · 3 comments · Fixed by #10627
Closed

Incorrect TableActionMenu placement when table is at the bottom of a longer page #10626

rilrom opened this issue Jan 17, 2025 · 3 comments · Fixed by #10627
Assignees
Labels

Comments

@rilrom
Copy link
Contributor

rilrom commented Jan 17, 2025

Describe the Bug

When a table is placed in a rich text field that is located at the bottom of a longer / scrollable page, the TableActionMenu is misplaced. It seems to be even more prominent when the browser is not the full-width of your monitor or browser dev tools are open.

incorrect-table-action-menu-placement.mp4

Link to the code that reproduces this issue

https://github.com/rilrom/payload/tree/issue/table-action-menu-incorrect-placement/test/_community

Reproduction Steps

  1. Enter in a lot of content to allow the table to be at the bottom of a scrollable page.
  2. Add a table.
  3. Attempt to access the table action menu.
  4. Placement is incorrect, sometimes being completely off-screen.

Which area(s) are affected? (Select all that apply)

plugin: richtext-lexical

Environment Info

Payload: 3.17.1
Next.js: 15.1.4
@rilrom rilrom added status: needs-triage Possible bug which hasn't been reproduced yet validate-reproduction labels Jan 17, 2025
@AlessioGr AlessioGr added the plugin: richtext-lexical @payloadcms/richtext-lexical label Jan 17, 2025
@github-actions github-actions bot removed the status: needs-triage Possible bug which hasn't been reproduced yet label Jan 17, 2025
@rilrom
Copy link
Contributor Author

rilrom commented Jan 17, 2025

I have resolved this in my own internal project, I will create a PR for it.

Copy link
Contributor

This issue has been automatically locked.
Please open a new issue if this issue persists with any additional detail.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 22, 2025
Copy link
Contributor

🚀 This is included in version v3.19.0

@github-actions github-actions bot unlocked this conversation Jan 23, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Jan 23, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants