Wordgard failed that test. Inputs coming from autocorrect or the keyboard suggestions are swallowed and delete the partially typed/misspelled word.
Both mobile Safari and Chrome Android do a ton of weird things that their desktop siblings don't, and play loose and fast with standards, so getting things to work correctly there tends to involve a long tail of hacks. Wordgard will get there but the focus before this first release has been on architecture.
There have been several efforts over the last couple decades to add a proper rich text element to the web. I don’t know why they have all failed - I guess it’s a large, complex and thankless task. It’s a pity. Proper native rich text support is one of the web’s big blind spots. It’s a problem native platforms have solved decades ago.
The right fix is for browsers to have a real rich text element of some sort. Then editors wouldn’t need all their hacks. And mobile browsers would be able to behave correctly when you tap on some editable rich text.