Rich Text Input has Arrived!

Thank you to the @weweb-team ! I’ve been waiting for this and am so excited to use this new element

4 Likes

Thank you @weweb-team! Dropped in beautifully, noticed a few things in the editor:

  1. Weird jump on my form when interact I with the menu. Seems to be related to a required field above that is empty. See video:
  1. Any way to turn off some buttons? I would like to keep responses more consistent, and it would save space / reduce clutter.

  2. Would like to add inline images as a feature request, stored in Xano preferably.

This is great to finally have this input! Plan to publish soon and start getting feedback. Thank you!

3 Likes

Yes very excited for this feature. I’m having some trouble using it in a Modal. When I try and add bullets, numbered lists the modal keeps closing.

I’m also seeing this error message pop up after it closes.

2 Likes

Thank you for all your feedback about this new element!

Sweet! I’m pumped for this.

I’m having some trouble using it in a Modal. When I try and add bullets, numbered lists the modal keeps closing.

I’m also seeing this error message pop up after it closes.

Thanks for pointing this out, @patopt. My first was going to be in a modal in a client app, so I’m going to hold off and wait to see some of these kinks worked out.

Following along :eyes:

The link button seems to trigger a change page workflow, even though I didn’t add any workflows to the element. Any ideas?

1 Like

We logged a bug yesterday: buttons triggers the submit of the form. This will be updated soon

1 Like

@aurelie I have a question, how should I store the rich text input as messages in my database? What type should I use? json/textfield? I use supabase

You can use either, but textfield should be enough. The content is exposed as HTML inside a string. :slight_smile:

1 Like

Thank you @Alexis