Gboard sometimes fires keydown and keyup events twice for a single key press and if that happens for the last key you press before selecting an emoji from autocomplete, you’ll get a crash. Ok, I’ve looked into this again today and managed to repro after switching the virtual keyboard on my phone to Gboard. Having autocompleteOptions be from the scope of the parent closure from two levels up is also quite weird and makes the code a bit hard to follow up/debug. At first I was suspecting this PR from I added quite a few breakpoints and can’t really find “who” is mutating autocompleteOptions and setting it as null. Follows the stack trace: _application-bfbda341c2eb6dd7d61c681e17bdccec057c30e045ddc332927a7363150e9b1b.js:16386 Uncaught TypeError: Cannot read property '0' of nullĪt HTMLLIElement.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |