Mevlüt Canvar

It's strange, I experienced this on a nuxt.js app then I register the component(despite no need to do that), it solved the issue.

I will send this issue link to the support.

Using a single config object on several froala elements cause the exception. The bug added by them to fix in the next editor release and they suggest using separate config...

@rcheung9 I've tried didn't help then I wrapped froala element with a component([gist](https://gist.github.com/crx4/65f72c3713a72361bd97511a99b8db71)). Its property returns a single config object.

@juliarosales I use "vue-froala-wysiwyg": "^3.1.1-1" version, please check your version. Another workaround: If you are ok with using different config objects for each of your froala editors, you pass directly...

@juliarosales Based on repo README, I only use "vue-froala-wysiwyg" dependency, you can try removing the other and use the gist I provided. Or, I guess you have PHP backend, you...

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...

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...

Looking forward to this for a bit of time. I am really excited!

> who the hell is using raspbian default user pi for doing anything else than booting the os creating an individual admin account? > > For me it is best...