Sorry for the late response.
Our software engineers' investigation points to WhatsApp text buffer management as the culprit. Here's how they explained it:
For this particular app, this problem happens only if we're trying to recapture the only word in the text buffer. It works fine if there are more than one words in the text buffer. Seems there is bug in this application’s text buffer management.
Notice that when the problem occurs, the inline word does not have the underline. This is because to recapture a word, we first copy that word into our text buffer, delete that word, call core recapture function, build the word list, then display the word list and the inline word.
But for some reason, WhatsApp does not delete the word and did not render the inline word. And if we press the delete key again, it then displays the inline word after the word that should have been delete but it was not. So we believe this is a bug in WhatsApp.
Moving forward, we suggest:
1) As a workaround, long-press on the delete key to delete the only word in this text buffer.
2) Report the problem to the WhatsApp development team.
About trace mode in URL entry box: The fact that you cannot use the FlexT9 Trace feature in the URL entry box is intentional by design since it was discovered that tablets maximize the input buffer when the URL is in focus. As a consequence, the entry box fills the entire viewable area of the screen -- you would no longer see any part of the webpage you were on.
Note that our engineering team is following closely this situation with tablets and will look into findind a workaround or improvement for it.
As for the case toggle and trace shortcuts, we have received similar suggestions and feedback from other users and we have forwarded them to our Product team. These features will be considered in future releases.
Thanks for the feedback!
Sunday, July 10, 2011
Nuance responds to flext9 bug reports/enhancement requests
i decided to contact flext9's technical support about some of the things i'd found from using their keyboard (see previous post). it wasn't quite the 48 hours suggested by their submit a ticket page, but they did eventually reply after about 2.5 weeks, and with some detail: