Ok—I’ve tried a bunch of things, and here’s what seems to happen:
- When you start typing, Mailspring enters text composition mode with the dropdown.
- When you press enter to confirm your typing and advance the text cursor, it works fine. (I think?)
- When you press TAB to control the composition dropdown (on the mac), it transfers keyboard focus to the To field and inserts the text suggestion there instead. (BAD)
- When you click something to blur the composition dropdown and save your current composition, Mailspring enters a weird state where the text is still there but is not selectable. If you type another phrase, the text is overwritten (BAD)
Does that cover your scenario? I can’t quite tell in the GIF how you are exiting / confirming the text when it disappears.
Unfortunately, I think these problems are probably upstream in the Slate text editor. It looks like there are quite a few known problems that the maintainers are merging in to ianstormtaylor/slate#2368. I will debug exactly what is happening, especially with the focus issue, and see if I can fix that on our side.
I’m very sorry but I don’t think this will be fixed in time for the 1.6.3 release tomorrow. There are a few other important bug fixes I want to get out, but I’ll make sure to investigate this early this week.
Hey @kometchtech, it looks like this works a bit better in the Slate examples (https://www.slatejs.org/#/rich-text) so I’m trying to narrow this down more and see what’s going on. Maybe there is something we can do today.
It turns out that that this issue may be specific to our text editor and Chrome-based browsers. (When I posted above I was using Firefox!) I filed a bug with at least one behavior I observed: ianstormtaylor/slate#2906.
It looks like we may be able to patch around this though, looking to see now.
(Originally posted by bengotow on GitHub.)