Hi @rico.trevisan
Thanks for the update. It would be great if it could erase formatting that doesn’t come from Tiptap as well. On the video below, I copy pasted content from a website. The first paragraph seemed to be cleaned up by the plugin (?) but not the second. And the ‘cleanup’ action doesn’t remove formatting.
Any help would be appreciated 
Could you share that example? If you refresh the page, does that HTML renders the same way?
Which version are you using?
I will try to find a way to handle this better inside the plugin.
In the meantime, what I do in this case is:
OK thanks for the info. I use the very last version (3.22.5).
I don’t use a collab server at the moment. I have too many users x pieces of content. It would be too expensive for not enough value added. I’m starting to think I’ll put on guardrails on multi-editing.
Yes, the content renders the same after reload. It actually happens the same way on your test app : the pasted content’s formatting is not removed…
As for my problem with the actions pushing the cursor, it still happens event if I remove the ‘when tiptap content is updated’…
Thanks
I just pushed a version that tries to handle the cursor better but I doubt it is a great solution.
For multiplayer, you could setup your own server with PartyKit on Cloudflare: Deploy to your own Cloudflare account | 🎈 PartyKit Docs
You could have a server without any persistence – meaning that the collab server would always pull the data from Bubble.
Then you have to create an endpoint in your Bubble app that can receive the collab server’s webhooks to then update the doc in your Bubble server.
Hey @rico.trevisan
Thanks for the update. I tried the latest version. The cursor jump seems to happen less often but it still happens sometimes and it doesn’t register the click when it happens (like before). I still don’t understand why it happens on my app and not in your demo…
Partykit + Cloudflare seems interesting 
@rico.trevisan Love the app! It seems like the collaboration is no longer working or set up is a bit unclear. I have tired tiptap cloud and also liveblocks but it looks like the app is not initiating the socket properly. TipTap has update their language around keys and id’s that dont quite match with the app’s fields.
Do you have a template example of collab working?
Thanks!
@rico.trevisan I would second this. not sure why but I can not make the collaboration work. the console says “debounce done, updating content“ but I can not see the collaboration UI when I am using two different browses. will send you the link just in case you have to check it out.
appreciate your amazin work on this plugin! thanks
Thanks for the bug reports. I’ll work on this in the next 2 days and get back to you guys.
Huge cleanup incoming.
Tiptap v3 UpgradeThe entire plugin has been upgraded from Tiptap v2 to Tiptap v3 (@tiptap/core ^3.0.9 and all extensions). This is a major upgrade that brings performance improvements, new APIs, and better extensibility.
^3.0.9^3.2.2 to ^3.4.4History extension with Tiptap v3’s UndoRedo extension (History is automatically disabled when collaboration is active)TableKit with individual Table, TableRow, TableHeader, and TableCell extensions for finer control
Architecture RefactorMajor refactoring of the plugin’s internal architecture for better maintainability, reliability, and performance.
window.tiptap namespace: All libraries are now exported as a single organized window.tiptap object instead of scattered window.tiptapXyz globals. The object is structured by category (Core, Basic nodes, Formatting, Block elements, Lists, Advanced, Styling, Interaction, Utilities, Collaboration, Third-party)UndoRedo, TrailingNode, Focus, Selection now available from @tiptap/extensionsinitialize.js: The ~760-line editor creation logic that previously lived in update.js has been moved to initialize.js as instance.data.setupEditor(). update.js is now a lean ~110-line file that handles property changes onlyinstance.data.applyStylesheet(properties) function callable from both update.js and the collab retry path, eliminating duplicationshared.html to headers.html: All scripts (dist.js, lodash, tippy.js styles) moved from the plugin-level shared.html to the element-level headers.html with defer attributes for better loading performanceshared.html cleared: No longer loads any scripts at the plugin level
Collaboration ImprovementsSubstantial improvements to the real-time collaboration system across all three providers (Tiptap Cloud, Custom Hocuspocus, Liveblocks).
maybeSetCollabInitialContent() helper handles the race condition between provider sync and editor creation — initial content is set on whichever fires lastonSynced may not fire reliably in all providerscollab_status (text) — current connection status (e.g., “connected”, “disconnected”)collab_synced (boolean) — whether the document has synced with the servercollab_connected_users (number) — count of connected collaboration userscollab_status_changed (event) — fires when the collaboration status changescollab_synced (event) — fires when the document syncs
Auth Token Action RewriteThe server-side JWT action has been completely rewritten and renamed.
Document names (comma-separated) — replaces the old Doc ID + Doc ID (list) fields. Now accepts a comma-separated string of allowed document namesApp ID — included as the aud (audience) claim in the token for securityUser ID (sub) — included as the sub (subject) claim for traceability and auditingExpiration (seconds) — configurable token lifetime (default: 86400 / 1 day). Previous version had no expiration
New Featuresis_empty (boolean) — reflects whether the editor content is empty, updated on every transactioncan_undo (boolean) — whether an undo operation is availablecan_redo (boolean) — whether a redo operation is available[Tiptap] messages to the console. When disabled, no console output is produced (replaces scattered console.log calls)
Bug FixesgetSelection fixed: The selectedHTML state now uses generateHTML from the window.tiptap namespace with the editor’s actual extensions, producing correct HTML output
Extensions RefactorThe old error-prone comma-separated list of extension names has been replaced with individual yes/no toggles for each extension. Each toggle is organized into its own labeled section, making extensions easy to discover, toggle on/off, and control dynamically with Bubble expressions.
CSS Override Fields CleanupAll advanced CSS override fields have been renamed, documented, and converted from large textareas to compact single-line inputs.
| Before | After |
|---|---|
h1_adv – h6_adv |
H1 CSS override – H6 CSS override |
p_adv |
Paragraph CSS override |
Image properties |
Image CSS override |
YouTube (duplicate name) |
YouTube CSS override |
Blockquote styling |
Blockquote CSS override |
Highlight CSS |
Highlight CSS override |
Bullet lists CSS / Number list CSS |
Bullet list CSS override / Ordered list CSS override |
link_adv, link_unvisited_adv, etc. |
Link CSS override, Unvisited link CSS override, etc. |
CSS for base div // override |
Base div CSS override |
All CSS override fields now use compact inputs (use arbitrary text for more room), and have documentation explaining that they inject raw CSS that overrides the preceding settings (size, color, weight, etc.).
Preserve Attributes Fields Renamed| Before | After |
|---|---|
preserve_attributes |
Preserve HTML attributes |
preserved_attributes |
Preserved attributes (read-only) |
preserve_unknown_ta... (truncated) |
Preserve unknown HTML tags |
All three fields now have documentation explaining what they do and how they relate to each other.
Property Panel ReorganizationThe entire property panel has been reorganized into a clean hierarchy: General config → Stylesheet → Extensions (with toggles + related settings) → Collaboration → Debug mode.
Cleanupreset.js now cleans up collab retry timers and sync polling intervals instead of just loggingreturnAndReportErrorIfEditorNotReady)console.log calls replaced with the instance.data.debug() helper, controlled by the Debug Mode field@rico.trevisan amazing work, many thanks for your efforts!
just sth that I still cannot understand (and probably not related to this new version): how can I make the collaboration cursor look more like the one that you have in the first post here rather than the one I have right now (it is just a new line with the name of the editor)? is it sth I have to do in bubble or is it some configuration in the plugin? thanks
It was a bug, fix in…
New Extensions
has-focus CSS class to the node where the cursor is currently positioned. Enables styling the active block — e.g., a subtle background or left border on the focused paragraph. Configurable mode: deepest (default, innermost node only), shallowest (outermost node only), or all (all ancestor nodes)..selection { background: #accef7 }) is provided automatically. Includes a Selection CSS override field to customize the highlight styling. CollaborationEach collaborator’s cursor renders two elements:
.collaboration-carets__caret) — a thin vertical line at the cursor position, colored with border-color from the user’s cursor_color..collaboration-carets__label) — a floating tag above the caret showing the user’s name, with background-color set to the user’s cursor_color.The plugin provides sensible defaults (12px font, 600 weight, rounded corners, positioned above the caret). To customize, use the Cursor label CSS override field. Any CSS you add is injected into the .collaboration-carets__label rule and overrides the defaults.
Default label styles:
.collaboration-carets__label {
position: absolute;
top: -1.4em;
left: -1px;
font-size: 12px;
font-style: normal;
font-weight: 600;
line-height: normal;
user-select: none;
color: #0D0D0D;
padding: 0.1rem 0.3rem;
border-radius: 3px 3px 3px 0;
white-space: nowrap;
/* background-color is set inline from cursor_color */
}
Example overrides:
font-size: 14px; padding: 0.2rem 0.5rem;opacity: 0.7;color: #fff;border-radius: 8px; Bug Fixes.collaboration-cursor__caret / .collaboration-cursor__label but Tiptap v3’s CollaborationCaret extension renders with .collaboration-carets__caret / .collaboration-carets__label. The floating name label now displays correctly with proper positioning, styling, and background color.Fixing some old pains with my buddy Claude
Bug FixessetContent(). However, collaboration uses a Y.js CRDT document as the source of truth, and setContent() replaces the entire document — destroying the Y.js state, losing remote edits, and causing content duplication or cursor jumps. When both were on, every user was continuously writing HTML to the same Bubble field (their own and remote changes), creating race conditions and feedback loops that corrupted the collaborative document. Now, when collaboration is active, auto-binding writes and read-backs are suppressed. The collaborative Y.js document takes priority as the single source of truth. A one-time debugger warning is shown if both are enabled. States (contentHTML, contentText, contentJSON) and the contentUpdated event continue to work normally. DocumentationThat’s some solid refactoring. Properly fitting code blocks into Bubble’s plugin environment is always a pain.
New Options on Existing Extensionstel, mailto, ftp). Comma-separated.@). Use # for hashtags, etc. New CSS Override Fields<hr> elements.<code> elements (does not affect code inside code blocks).<pre>) elements.<sub> elements.<sup> elements. New ExtensionsDetails / Accordion — Collapsible <details>/<summary> blocks for FAQs, toggleable sections, and accordion-style content. Includes:
Invisible Characters — Shows paragraph marks (¶), spaces (·), and hard breaks for power users who need to see whitespace. Includes:
Bug FixesA few of you have asked for the comments extension. However, that is a paid plugin and I cannot add to this plugin. You have 2 options:
FYI: Some of the other paid extensions and the corresponding plan.
| Extension | Plan |
|---|---|
| AI Generation | Start |
| AI Toolkit | Addon |
| Comments | Start |
| Compare Snapshots | Team |
| Export (docx/odt/md) | Start |
| Import (docx/odt/md) | Start |
| Pages | Team |
| Server AI Toolkit | Addon |
I’ve (re)launched a collaboration service (like Tiptap.dev or Liveblocks). There’s a free tier so you can give it a try: https://tiptap.rico.wtf/
It is still in beta so all feedback is welcome.
Bug Fix — Table selectionFixed an issue where selecting text inside a table cell with the mouse could cause the entire table to appear highlighted instead of just the text within the cell. This happened because prosemirror-tables converts accidental table-level selections into a cell selection covering all cells. A new Allow table node selection option lets users control this behavior.
New Table OptionsFour new configuration options for the Table extension:
true. Disable for simpler tables with equal-width columns and no resize handles. New Server-Side Actionpayload.document){ "default": { "type": "doc", ... } }){ "type": "doc", "content": [...] })"default") — for custom Hocuspocus setups using a different Y.js field namehtml (text), error (text), returned_an_error (boolean) Editor Rebuild on Document ID ChangeWhen the collaborative document ID (collab_doc_id) changes at runtime, the editor now automatically tears down and rebuilds with a new provider connected to the new document. Previously, changing the document ID required a page reload.
collab_doc_id changes while the editor is active in collaboration mode, the existing provider and editor are cleanly destroyed (connections closed, timers cleared, DOM removed) and a fresh editor is created for the new document.Collaboration document changed — Fires just before the teardown begins, allowing workflows to react to the document switch (e.g., save state, show a loading indicator).teardownEditor() helper that handles full cleanup: collab sync polling, retry timers, debounce timeouts, provider destruction, editor destruction, DOM removal, and state reset. Used by document ID change detection, collab auth failure retries, and element reset — eliminating duplicated teardown logic.reset.js now uses the shared teardown for complete resource cleanup instead of only clearing timers. Minor Improvementsapp_id collaboration field has been renamed to match Tiptap’s current naming: Doc Server ID.collab_status values (disconnected → connecting → connected → synced) are now documented directly in the plugin property panel for easy reference.