Open VAUNT opened 5 years ago
I'm running into this exact issue. I wonder what is the problem here :(
I have the same issue too ...
I have the same problem when I use multiple froala tags in a form.
Unfortunately, I had to remove this repo from my project. I installed froala's main repo and use the event contentChanged
for initializing the editor.
@VAUNT any update on this?
There have been multiple posts on this issue. Wonder if this project is still being maintained?
Not really sure, last commits are from January, so not that long ago...
If this repo was a third party I would ok with this situation. But it is official and still nothing happening about this, kinda sad...
Until the bug is fixed by the company, I wrote a wrapper to handle it.
The saddest part is that we pay for a license and annual support but the devs don't even reply to a critical issue like this, for over half a year now.
I fix this issue with a v-if into the froala tag, i hope it helps someone
<froala
v-if="!loading"
id="edit"
v-model="resultHtml"
:tag="'textarea'"
/>
data() {
return {
loading: true,
resultHtml: null,
};
},
mounted() {
this.resultHtml = '<h1>Test</h1>';
this.loading = false;
},
@farena I try with your solution and this fixed my issue. Thanks!
Hello!
When on the page where I have many instance of froala, I found this error and the initialization of froala is very slow, need help! Thank you.
the error is same here https://github.com/froala/vue-froala-wysiwyg/issues/111
the save is done correctly but the initialization is really slow