I tried a bunch of stuff yesterday and failed. Given the twisted history that I have with autobinding, I think that the wise thing to do is to turn it off until I grow some further skills.
If anyone has ideas, let me know.
I tried a bunch of stuff yesterday and failed. Given the twisted history that I have with autobinding, I think that the wise thing to do is to turn it off until I grow some further skills.
If anyone has ideas, let me know.
When the Input Enabled checkbox is unchecked (so the input should be disabled), it is a little buggy. Sometimes when a page is loaded, the tiptap input is still enabled and users can still type inside the tiptap for a short while before the input is disabled. Its almost like the tiptap is enabled by default when its loaded and only becomes disabled when it is fully loaded. Is there any way to fix this so that it is disabled immediately when the page is loaded?
Thanks
The plugin has stopped working completely. I think it was because of the Bubble update. Now itās showing a broken plugin message:
The plugin Rich text editor (Tiptap.dev) / action H3 a Tiptap threw the following error: anonymous@PLUGIN_1670612027178x122079323974008830/āRich-text-editorāTiptap-devāelement_actionāTiptap-H3-.js: 3:72
lib-browser/pluginservice.js/pluginservice3.create_code/<@https://mgnifi.co/package/run_debug_js/095afa0ea36b23400aaff758552e9eca28e213d55b503519ee041993dcf6a8e0/xfalse/x28/run_debug.js:481: 677
lib-browser/pluginservice.js/_interpret_raw_plugin_def/run/</</</</<@https://mgnifi.co/package/run_debug_js/095afa0ea36b23400aaff758552e9eca28e213d55b503519ee041993dcf6a8e0/xfalse/x28/run_debug. js:608:3485 (please report this to the plugin author)
Would you mind sharing a bit more detail on your setup? It would be useful for me know what the javascript console is displaying, too.
Iām unable to reproduce this with my test app: Bubble | No-code apps
It was working normally until the Bubble update, but now it gives this error.
Follow recording:
Thanks. While trying to check the error this morning I saw that some plugins of mine were throwing a similar error. Iāve reported a bug to Bubble because as far as I could troubleshoot, the error is not on the plugin side.
Thank you very much! I hope Bubble solves it, because the plugins you created are excellent!
I discovered here that āfloatingMenuDivā is undefined.
Maybe itās happening if the script is trying to access a DOM element that doesnāt exist or hasnāt been loaded yet, or something like that.
Maybe Bubble changed the structure of this element.
Any news @rico.trevisan ?
None yet. Iām on holidays with bad Internet connectivity.
Any news @rico.trevisan ?
Iām having all sorts of challenges with all the collaboration libraries (again!). Iāll likely trim the plugin to only the editor and spin out a different one for collaboration. Give me a couple of days.
I will have to remove autobinding.
Todayās goal was to fix autobinding, prohibit actions from running before the editor is ready, add a couple more style controls, and finally record a tutorial.
Nope.
Iāve spent the whole day today battling autobinding x Tiptap. I have been unable to find the root cause of autobinding wiping the editor contents. No luck.
The closest Iāve come was to identify that v2.7.1 works but the following version doesnāt. I figured I should be able to restore my dev environment to that version and rebuild from there. Nope. The same exact code doesnāt work in my dev environment.
Luckily there are ways around autobinding. In the next version:
Content updated
trigger so that you can hook a Save
function and it wonāt explode your WU.body
aka has no heading tags applied to it.As explained above, thereās a bug somewhere between Tiptap and Bubble that clears out the editorās content after every save. Iām still looking for a solution but it has to go for now.
Commands now will not run if the editor is not yet active.
With these things out of the way, I will take a look at your bug report.
And if you expand the debugger
ul
(aka bullet lists) and ol
(aka numbered lists)cc: @v.chavda
Hey @rico.trevisan, incredible plugin. Thanks!
Quick question around the YouTube feature. Explained here: Loom | Free Screen & Video Recording Software | Loom
Any help would be much appreciated.
Cheers,
Daniel
Thanks for the bug report. Let me take a look.
Wow, something very funky happening there. I can reproduce it. The weird thing is that the src remains if you export the JSON.
Iām not sure whatās causing it. I canāt find any code in the extension-youtube
library that would strip it out. Iām going to keep investigating. Iām wondering if thereās some code to prevent injection attacks that is seeing a youtube url and removing it. Weird.