Shouldn't the Floating-UI library be considered instead of TippyJS?

[GitHubish]

FloatingUI has been completely rewritten in Typescript and is very modular, powerful and lighter than TippyJS with full documentation. So many reasons that it seems to me that it would make sense to replace TippyJS. What do you think about it?

any plan to refactor with Floating UI?

[bdbch]

For now we don't really considered changing the popover/popup solution but everything is open for discussion. Are there more information on how lighter it is or any other direct differences between Tippy and FloatingUI?

[SalahAdDin]

How ended this discussion?

[bdbch]

FloatingUI is implemented in 3.0.0 going forward

[websiddu]

Bumping the discussion up, has no updates since Feb 2022 https://github.com/atomiks/tippyjs
While floating ui is constantly developing — https://github.com/floating-ui/floating-ui

floating ui is used in popular frameworks such as react radix and vue-raidx, currently if you are using tiptap and a one of those libraries tippy is adding significant size along with floating ui library.

Please do consider converting to floating UI @bdbch is you are open to it I happy to start working on a PR.

[ajayvignesh01]

+1

Even the tippy.js maintainers advise to use Floating UI

[james-pratama]

+1

[nperez0111]

I'd be happy to accept a PR on this, if you are still willing @websiddu

[SalahAdDin]

@websiddu will you?

[bdbch]

Tippy was deprecated from Tiptap and was replaced by FloatingUI with 3.0.0

[bdbch]

We don't want to support Tippy.js anymore. What issues are you running into styling related?

[tjbck]

Hi, thanks so much for the quick response and for all the hard work that's gone into Tiptap 3.0, it's really appreciated.

To give some specifics: most of our issues are related to z-index handling. With tippy.js, popups consistently appear at the very front layer, regardless of the app context. With FloatingUI, we're running into two problems:

• Initialization: The popup is displayed by default when it should be hidden by default. This could definitely be a compatibility issue on our end (we're using Svelte/Vanilla JS), but it's been tricky to debug.
• Layering & Placement: The popup isn't being reliably positioned above everything else, z-index seems to have less predictable behavior, and sometimes the popup gets clipped or hidden behind other elements. It also seems to extend the container div, whereas tippy.js rendered the popup outside the flow so it could "break free" from any stacking contexts.

If you have any recommendations for properly handling FloatingUI’s layering or best practices for initialization/visibility (especially in non-React setups), that would be super helpful!

Thanks again for your time and all the work you're doing to improve the library.

[tjbck]

Screenshot by @Classic298

[bdbch]

That's weird, the menu should not be visible from the get-go but should just be mounted if shouldShow returns a truthy value.

What does your Menu implementation look like?

[tjbck]

@bdbch Using with vanilla js, is there a recommended reference implementation?