This is a slightly different case than #5003 - resulting text after pending text insertion *does* exist in hint list.

The **current code** eats the `Enter` (or `Tab`) key. This causes pending text to update hints so that they are further filtered and remain displayed, but some user input is ignored.

**Another option here** would be to reject (not eat) key so that hint list gets dismissed and `Enter` (or `Tab`) gets inserted in page. I wasn't quite sure of how the intent should be interpreted.