Josh Goebel

So can we confirm this was a Chrome bug then that's being fixed in upstream Chrome? IE: Could this issue be closed now?

Original poster would need to close. I have no admin rights to this repo and original author seems to have moved on. I just try to help and direct people...

They work at the exact same level.

> it was printing unicode output to an ascii only environment What is the "ascii only environment" you are speaking of? I haven't heard of this from another else and...

@flareriderdash You may want to consider upgrading to my fork, as it does not have this problem (no fancy logo). https://github.com/joshgoebel/keyszer

@rbreaves This is really the same as the Alt issue... have you given it much thought? I'm working on it now and trying to decide the nuances... I'm calling it...

I feel like if my fork could resolve both the sticky issue and the unwanted keys issue that would be a good first release.

Note: It's also possible the timer could be infinite, but that would prevent using a single held modifier as a trigger for anything... For example: - I press and hold...

@nrsimha If you'd want to join the new discussion on this issue at my fork (where I've been trying to fix this): https://github.com/joshgoebel/keyszer/issues/9 I'd truly like to fix this, but...

Personally, this sounds out of scope to me... sounds like a great additional utility - a tiny piece of software that listened for globals and interacted with the window manager...