Okay, back againā¦ but I just want to say @rico.trevisan you are officially my favorite Bubble plugin developer. I wish you had paid plugins, because Iād love to feel like Iām giving back to you for your awesome work.
This plugin has me excited (for the first time ever) about building rich text experiences on Bubble. Iāve pretty much found the solution to my previous comments. But one thing I am struggling to figure out now is:
When a user pastes Markdown text, the tiptap field doesnāt automatically convert it. It catches the inline code, bold, italics, and strikethrough, but none of the other formatting such as headings, code blocks, ordered/unordered lists.
Another issue - it looks like the Initial Content field is being used more as a data source field. If I understand it correctly, the initial content should only be whatās loaded on initial page load and subsequent database changes to that field should not impact whatās seen on the front end (until a page refresh); however, whenever I update the database field specified by initial content, itās reflecting on the front-end immediately. This shouldnāt be the case, should it? It leads to a pretty funky experience where, as Iām typing, the database is updating on the back-end and text is reverted on the front-end to the value written to the DB, even if Iāve already written more.
Iāve find a problem. My users are dropping base64 images on editor and itās breaking my application. If you could add an option to enable/disable base64 dropping it would help me a lot.
allowBase64
Allow images to be parsed as base64 strings <img src="data:image/jpg;base64...">.
Hey @rico.trevisan - I donāt believe setting colors work correctly.
I have tried manually setting colors, and dynamically setting them. The highlight only stays yellow, and the change color action doesnāt do anything.
Yes, thereās one step I forgot to mention ā you have to add Color to your list of Extensions. Iāll add a debugger message so that you at least get some feedback.
This is just an opinionated suggestionāfeel free to ignore.
I think it would be better for the floating bar to appear BELOW the line that it will apply to, rather than inline. It feels like itās in the way before the user starts typing.
Turn most of your actions into singular but dynamic actions.
For instance - setting Heading, you can just make one action and have it so you have a drop-down option for all the specific headings. That would give us ONE action (āSet Headingā) with a dynamic property or option list.
Or the Add/remove items, you can just make the actions add OR remove based on a dynamic yes/no.
If you need help optimizing it, let me know - been going through my plugins and making sure they are as dynamic and modular as possible recently.