When clicking on an input[type='text'] autocomplete suggestion, the keyUp event is fired but event.key is undefined. This causes some downstream logic that assume key is a string to throw.
This is happening in Chrome 71, unsure if it's a recent browser bug or not.
When clicking on an
input[type='text']
autocomplete suggestion, the keyUp event is fired butevent.key
isundefined
. This causes some downstream logic that assumekey
is a string to throw.This is happening in Chrome 71, unsure if it's a recent browser bug or not.