thomasgebets
thomasgebets
> Our customers also were experiencing this issue. We use quill via `ngx-quill` and the solution I came up with to fix this for all our quill editors was to...
Ok i have solved it by adapting in this manner: ``` const originalGetSemanticHTML = this.quill.getSemanticHTML; this.quill.getSemanticHTML = function (): string { return originalGetSemanticHTML.call(this).replace(//g, ''); } ``` Thanks a lot for...
This issue still persists, any timeplan, when this will be resolved @jhchen ? thanks!
Hi, did you somehow solve this issue? I'm currently also struggling to get the whole setup working..