The menu of a table cell is not displayed correctly on pages with a scroll bar

[radudevit]

Link to reproduction

No response

Environment Info

Payload: 3.0.0-beta.107
Next: 15.0.0-canary.104
Node: 20.17.0

Describe the Bug

table-action-menu-dropdown section doesn't appear as expected when page has a scroll bar and the user scrolls up.

Reproduction Steps

1. Create a collection with a rich text field, and add table feature to that rich text editor
2. Add more fields to that collection, before the rich text field - to have a scroll bar in the browser
3. Open the edit page of that collection
4. Create a new table in the rich text editor
5. MAKE SURE THERE IS THE SCROLL BAR AND YOU CAN SCROLL UP
   
6. Click on the menu of a cell. The menu dropdown is displayed
   
7. SCROLL UP A BIT
   
8. As you can see, the dropdown menu is not aligned correctly
9. If you scroll down to the bottom, as it was before - the dropdown menu is not shown at all on the screen, even though it is in the DOM
   

The dropdown menu should be displayed relatively to the cell the user clicked from.

Adapters and Plugins

No response

[GermanJablo]

I can reproduce two types of behavior:

• the menu follows the viewport when the cell disappears from the viewport due to scrolling.
• the menu disappears when the cell disappears from the viewport due to scrolling.

Both behaviors are reasonable, but what I have not been able to reproduce is your last 2 screenshots, where the cell is visible but the menu does not appear or appears in the wrong position.

Screen.Recording.2024-09-17.at.12.39.27.PM.mov

Your instructions are clear and the screenshots are very illustrative. I think I will need some repro in the form of code.
You can create your own repository or tell me how to reproduce it in the Lexical repository after setting up a mongodb instance in .env and running pnpm dev fields (Info here)

[GermanJablo]

Closing because we can't reproduce it. Feel free to open a new issue with more information.

[github-actions]

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