Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xterm weirdness on Android Chrome #14

Open
ajdlinux opened this issue Feb 27, 2017 · 5 comments
Open

xterm weirdness on Android Chrome #14

ajdlinux opened this issue Feb 27, 2017 · 5 comments

Comments

@ajdlinux
Copy link
Contributor

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...

@raggi
Copy link

raggi commented Feb 27, 2017

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.

@raggi
Copy link

raggi commented Feb 27, 2017

Looks like it is using keydown, so my intuition is wrong.

@jessfraz
Copy link
Collaborator

jessfraz commented Jun 6, 2018

is this still happenning let me know and i will reopen

@jessfraz jessfraz closed this as completed Jun 6, 2018
@raggi
Copy link

raggi commented Jun 6, 2018

Yup, still happens

@jessfraz
Copy link
Collaborator

jessfraz commented Jun 6, 2018

thanks thanks, I reopened :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants