Hey, i found a strange behavior when embedding the scripts/using html widget
I had some similar frustrations trying to render a widget within a html element. The widget kept rendering below/outside the html element (and therefore appeared behind my button element at times).
I ended up removing any references inside the html code, and only use the html attributes section.
The result is a big empty html element within the editor, but finally renders correctly when published.
Editor view
Published view
i
1 Like
Hi,
due to how the editor is build (two apps, and your app preview in an iframe), you should never use document but wwLib.getFrontDocument()
Then I discourage using global variable directly, and always get the front windows first wwLib.getFrontWindow().My_GLOBAL_VARIABLES
For the html part, i think we should add a “onLoad” event, to be sure to execute the script after the html is generated
1 Like
It would be amazing if you guys made a comprehensive guide on how to embed scripts like this, and how the app works in the background as well when importing custom scripts, because as of now, it is really just trial and error, which costs many of us a lot of time → which means that it costs us money too 
Edit: one solution would be to not paygate the developers from using the custom plugins/components by a plan.
It’s not really possible that I have to do stunts to embed something that I’d be able to embed by copypasting HTML an some script tags in plain .html or an npm package with something like Vue. I understand this is a nocode tool, but this is really really terrible experience, to must spend hours on a dumb embed 
1 Like
Documentation and dev user experience is on our roadmap for the end of the year
3 Likes