fix(templates): added portalElement in floating-toolbar component.

[zhyd1997]

• added changesets
• updated components changelog

[changeset-bot]

⚠️ No Changeset found

Latest commit: 16297bc

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
plate	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 17, 2024 10:27am

[zhyd1997]

Example usage:

<FloatingToolbar portalElement={editorContainerRef?.current ?? undefined}>
  <FloatingToolbarButtons />
</FloatingToolbar>

[zbeyens]

Following shadcn pattern, we don't maintain/extend props since they're owned by the consumer. That means you should add this in your app. Thanks for reporting the bug though, if we have such example, we could use your fix.

[zhyd1997]

Hi @zbeyens

But it is hard to debug if the editor is in a dialog.

The devs will take a long time to figure out why the floating buttons have no tooltips and are not clickable.

[zbeyens]

Could you update the changelog?

[zhyd1997]

Sure, but I am on vacation in these 2 days, will update it asap, thanks 🙏

[zhyd1997]

Hi @zbeyens

Updated changelog done.