I copy and paste an image to the editor, then I CLICK NEXT TO THE IMAGE (to set the cursor on the on right side of the image);
Then I hit enter
The cursor should move to the next line
After I set the cursor next to the image, I should be able to type as well.
After hitting enter the cursor does not move to the next line
After typing, I cannot type anything
Forked the Init/Destroy demo from the froala website demo page
https://jsfiddle.net/nevaan9/9whcjqvr/3/
Mac 10.15.3
Chrome Version 80.0.3987.100
froala_issue.mov
@nevaan9 Can you confirm that the issue can be reproduced in this fiddle?
https://jsfiddle.net/dejan_m/og0hxf2t/3451/
@dejanmartinovic it seems to be working in that fiddle
I attached a video where this issue is still happening.
When hitting enter the whole image just moves, instead of going to the next line.
@nevaan9 @rogerfar We are aware of that issue. It occurs in the last release (3.1.0). Fix will be available in 3.1.1. Fiddle I've shared running the v3.0.6 and that's why you can reproduce it there.
@nevaan9 @rogerfar We are aware of that issue. It occurs in the last release (3.1.0). Fix will be available in 3.1.1. Fiddle I've shared running the v3.0.6 and that's why you can reproduce it there.
I had the same problem with version 3.0.6. The project is developed based on Vue I had the same problem with version 3.0.6. The project is developed based on Vue
@gagadzq Could you double-check the version? If you are using v3.0.6 can you recreate that issue in Sandbox?
@dejanmartinovic do you have an estimated date for the 3.1.1. release?
@dejanmartinovic do you have an estimated date for the 3.1.1. release?
Unfortunately no. Due to unforeseen technical issues, development had to roll the fixes in 3.1.1 into 3.2.0 which will be released this quarter. I'm sorry for not being able to provide more precise info.
@dejanmartinovic sorry, for the spam, but you mean Q2, correct? As in by June/July?
@gabaum10 That is correct. Version 3.2 will be released by the end of June (probably earlier)
@dejanmartinovic we are using V 3.2 and this issue is not yet fixed. What is the timeline?
This issue risks our project.
Most helpful comment
@dejanmartinovic do you have an estimated date for the 3.1.1. release?