It’s free as in beer . But I would like you to pay with feedback and requests. My goal is to treat this project as an open-source project, taking in pull requests and improving it for all of us.
Each little feature is accessible via workflows and have individual events that fire immediately. That means that you can create and control your own menu.
Keyboard shortcuts
Both for classical editor and markdown. You can set a paragraph to Heading1 either by typing ⌘ + ⌥ + 1 or by adding # at the beginning of a paragraph.
Elements
Paragraphs: bold, italic, underline
Headings - from H1 to H6
Images
Ordered lists
Unordered lists
Quotes
Links
Code blocks
Horizontal line
Text alignment: left, center, right (and justify)
Text highlighting
Tables
Roadmap
Current goal: Mentions
Next goal: Offline version
Offline mode
Releases
2.0.2: fixed library versions and unleashed autobinding
@rico.trevisan back with some more feedback (using version v.1.0.1 )
Issues
input is enabled option:
When check it works as expected;
When uncheck it doesn’t work as expected (input is still possible);
Responsive/layout behavior:
(context of use)
I’m using your plugin in a SPA
The tiptap editor is inserted into a floating group;
This floating group is used to create an edit notes;
I’m under the impression that in order to get inputted content in tiptap element, to scroll in a floating group, you need to enable the option “fit height to content” even though I have inf max height for the element.
Would you consider this to be expected behavior? Try it out yourself by replicating these steps:
In editor:
Create a floating group with scrollable content (e.g: text). Configure the floating group as you would for a SPA (fullcreen);
Create a second floating group and include the tiptap element. Configure the second floating group as you would for a SPA (fullcreen);
Configure the tiptap element to have no max height. Keep the “fit height to content” option unchecked;
In preview:
Insert a few paragraphs of text until text passes page fold;
Try to scroll (it won’t work)
Now, go back to the editor an enable the option “fit height to content”. Try to scroll again (it will scroll).
This behavior just doesn’t seem super intuitive (at least for me). Curious to know what you and perhaps others think.
I want to test it on a real app. To do that I need to publish a new version which will roll out to all of you. I’ll make sure to tag it as BETA. Try it out and let me know.
Could you show me your app? What do you mean when input is still possible? Can you type? Or are you referring to the actions (bold, italic, etc.)?
On my demo it seems to work properly.
Properly’ish. Typing input is disabled but actions still work. What’s the right approach / philosophy: who should be responsible to restrict it: the plugin or the Bubble dev?
A small quibble from a UI perspective. The cursor doesn’t change to a finger icon when you hover over a url. Not sure if this is under your control.
For the custom menu, can I highlight text and then click a custom menu button to act upon the highlighted text? Is there any docs on how to do this yet?
If I’m using the current Bubble RTE, is there any migration issues?
Lastly, based on previous discussions we’ve had, if I paste in an image, is it stored securely?
Just updated to beta version. From my brief testing, it does seem like auto-binding is working as expected! I’ll continue testing though and will report back
I’ve just realized that your demo actually has two pages… (index and doc). I completely missed the doc page (default goes to index ).
I see that you check a value and then based on that, the tiptap element is editable or not. I haven’t tried this approach. I’m just using the option shown in the screenshot above…
In any case, it’s not really a deal breaker for me at the moment, as I can just use an html element to display content vs enable/disabling input within tiptap.