Yep so there’s a incompatibility in a couple of specific configurations b/w quill’s library and inlining HTMLs (i.e. not using CSS). The benefit of inlining html is you can use the content directly outside their bubble app as an email template / other places without any css. The downside are these edge cases.
Now one option is I switch to using html which require’s the stylesheet to be present too. I’m just worried about this impacting customers who are using the html output as content outside the bubble app. Its’ a bit of tricky decision since people use the plugin for a variety of use cases. Hence haven’t rolled out an update till now. Currently looking into solutions if its’ possible for me to upgrade the plugin without a breaking change / give some sort of a workflow-step driven workaround.