New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 887782 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Typing before the decoders load can cause typos

Project Member Reported by shend@chromium.org, Sep 21

Issue description

Chrome Version: 71.0.3554.0
OS: Chrome

This is difficult to reproduce manually, but easy to do with an automated test.

1) Login
2) Open the virtual keyboard
3) Before the decoders finished loading, type "he"
5) After the decoders load, type "llo"
6) Decoder only sees "llo" and autocorrects it.

Can we queue up events in a buffer when the decoder is loading and then pass it on when the decoder loads?

I think it doesn't really affect users though...only automated tests.
 
He Darren,
We should not do in this way, since if decoder broken, then the keyboard hang.
Whatever decoder broken or not, we must handle key event at once.
It's different with virtual keyboard.
I see...I agree we should not block typing.

How about, we still allow users to type (like current behaviour), but we save the characters somewhere in a buffer. When the decoder loads, we send those characters to the language model so that the autocompletion gets the whole word.

I don't know much about how decoders work, so if this is too complicated then we don't need to fix this. I'll just run the automated tests with autocorrection off.
Status: Available (was: Untriaged)

Sign in to add a comment