Closed lexgp closed 2 years ago
Hi! Thanks for reporting. That's weird, I think it's a recent bug due to newer browser updates, I'm pretty sure it didn't happen the last time I released this package. I'll try to find a workaround to fix this. Thanks
Hi @lexgp Fixed in v2.0.4 and v1.2.7. Please let me know if you still have issues.
@motla Thank you, it has become much better. But I think the next problem has the same roots:
Thanks for reporting again!
On macOS it seems to have different behaviors with different browsers:
I can't work on this before September because I'm on holidays... In the meantime if you want to help and patch it yourself, you juste have to prevent the default browser action depending of the user input in the keydown event, like I did for the original issue you mentioned. Just add some more conditions on e.keyCode
. It should be pretty easy but I have no time to test it and release a patch properly right now.
I hope that helps!
Actually this is a bit more complicated than I thought because we have to detect if all the document is selected or not...
We should also set this.content = []
manually as the default action will be prevented.
Hi @lexgp I just released v1.3.0 for Vue2 and v2.1.0 for Vue3 which should correct your problem. Please let me know this if you still have issues.
Hello. I really like the component, but a small bug is confusing.
It seems that deleting the container in which the editing is taking place leads to an error