Revert "[lexical-playground] Fix: in playground show component-menu w…

[zurfyx]

Breaks internally, might need to revise the approach or our internal code...

…hen scroll (#6510)"

This reverts commit fd7a93d.

Description

Describe the changes in this pull request

Closes #

Test plan

Before

Insert relevant screenshots/recordings/automated-tests

After

Insert relevant screenshots/recordings/automated-tests

[vercel]

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	Aug 26, 2024 6:08pm
lexical-playground	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 26, 2024 6:08pm

[github-actions]

size-limit report 📦

Path	Size
lexical - cjs	29.38 KB (0%)
lexical - esm	29.24 KB (0%)
@lexical/rich-text - cjs	37.89 KB (0%)
@lexical/rich-text - esm	31.07 KB (0%)
@lexical/plain-text - cjs	36.49 KB (0%)
@lexical/plain-text - esm	28.41 KB (0%)
@lexical/react - cjs	39.61 KB (0%)
@lexical/react - esm	32.52 KB (0%)

[etrepum]

Can you put together a repro that shows what goes wrong with this approach? It fixed all of the positioning issues that we could find, this revert is an OSS regression

[ivailop7]

Maybe a complete rewrite of the floating elements - context menu and typeahead/mentions/hashtags suggestions is worth it, maybe using something like https://floating-ui.com/ that would handle all of the render details correctly. All of those popovers are playground-only, so it should be OK relying on a 3rd party package for the rendering of these two. Just food for thought.

[etrepum]

Yeah, Floating UI is what I used in the past for doing this sort of thing and it worked well. I don't have a strong opinion on whether we should have a dependency handle floating UI or have an in-tree implementation without known issues but we should certainly not have an in-tree implementation that we know is incorrect for the cases that we demonstrate.

[potatowagon]

Can you put together a repro that shows what goes wrong with this approach? It fixed all of the positioning issues that we could find, this revert is an OSS regression

reintroducing the changes back in #6566 but with gating so we can investigate internally and fix intern