We use the Froala editor (v2.x) in our Ionic 3 app. We've been using it for years and then just the other day, Samsung made an update to their keyboard app, which now causes the keyboard to close when backspacing in the Froala editor. This doesn't happen in other non-Froala text fields.
We've tried to reproduce it on 4 different Galaxy devices with no luck. However, it's not an isolate incident as we have over 50 reporters.
Also, we realize that this probably isn't the fault of Froala but looking for guidance :)
Tapping backspace deletes the previous character.
Backspace causes the Samsung Keyboard to close.
Unfortunately, we have no steps to reproduce. It's a mystery!
froala-editor: 2.9.8
angular-froala-wysiwyg: 2.9.8
Android: 9 and 10
We're using Ionic 3 so it would be the Android System Webview I believe.
I'll work on getting this.
+1
We noticed this today also. Can be reproduced on Froala's own website with latest version of Froala 3.x when using Samsung Galaxy s9 with latest Android Chrome browser.
After any space character has been deleted from the editor, all subsequent backspaces presses cause the keyboard to close, even though the cursor is still flashing in the editor.
I am using Froala 2.9.8 in an Angular application.
I am also experiencing this issue. We have an enterprise application which uses Froala, and our app is considered "down." The users are saying they cannot use the keyboard because it keeps disappearing. Many of our users have Samsung devices.
My hope is that we can find a solution to this issue quickly.
Here is a link to a video of the issue. You can see the keyboard closes when I hit the Backspace/Delete button.
You can also see the issue does not happen the first time I use the Backspace key, but only after hitting Backspace a few times.
The bug also happens with [return] key. (Line break/new paragraph)
On Fri, 4 Sep 2020, 01:08 Alex Barberi, notifications@github.com wrote:
Here is a link to a video of the issue. You can see the keyboard closes
when I hit the Backspace/Delete button.https://barberialexlive-my.sharepoint.com/✌️
/g/personal/alex_arbwebapps_com/Ec_z0HUZOO5Fkrv7CGDbDtIB5MMnPl1Z5HryRflfXovb3A?e=XeAyJg
https://barberialexlive-my.sharepoint.com/:v:/g/personal/alex_arbwebapps_com/Ec_z0HUZOO5Fkrv7CGDbDtIB5MMnPl1Z5HryRflfXovb3A?e=XeAyJg—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/froala/wysiwyg-editor/issues/4022#issuecomment-686788826,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ2SWSIE3WLMUFYLGNEUQHDSEAHU3ANCNFSM4QT372EQ
.
Appears to be a bug in Chrome...
https://bugs.chromium.org/p/chromium/issues/detail?id=1121179
Saw a similar issue on the TinyMCE github.
This is Chrome's bug.
It has been fixed, about 17hours ago.
https://bugs.chromium.org/p/chromium/issues/detail?id=1121179