xterm weirdness on Android Chrome
Per @raggi, the console behaves strangely on Android Chrome. https://photos.google.com/share/AF1QipNiK_IQM4HrtI5_9uzfJmkC1-8-tYJs4BlilVm-3M2PoRud3YoJ2umWvKE3yQ45Ig?key=YzhoeWg1c1UwZXVyaUQ3QWNiOC1yX1N2YWlSNl9B
I suspect it's probably a bug upstream in https://github.com/sourcelair/xterm.js, will investigate...
FYI, in the past I've had great success with hterm.js (the one that chromeos uses in crosh). https://chromium.googlesource.com/apps/libapps/+/HEAD/hterm
I think (just based on behavior) this is working by an input box underneath and is grabbing value out of the input events while trying to keep some off-input source of truth, and they're getting out of sync. I think it'll want to move to key events instead.
Looks like it is using keydown, so my intuition is wrong.
is this still happenning let me know and i will reopen
Yup, still happens
thanks thanks, I reopened :)