With the short-word-suppression Ranker model we're seeing the ability to tap-select a short word only when done right after a tap-select on a regular word nearby.
We need to investigate whether this is a CS problem or in Ranker -- I'll take a look.
I'm pretty sure this bug is in Contextual Search. It's location-related, not timing related. When tapping on a word nearby when the Bar is showing we don't close and reopen the Bar, we just update the search. I suspect the code-flow is updating the existing example in this case adding a second set of datapoints to the proto.
The problem is that the Search is still in progress and the Bar still active when the retap is processed. We need to detect this and log the outcomes and reset the logger in order to separate the features of the previous gesture from the new gesture.
Summary: [TTS] ML Retap: Tap on a short word selects when quickly following a nearby word (was: [TTS] Tap on a short word selects when quickly following a nearby word)
Comment 1 by donnd@google.com
, Nov 16 2017