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

Dead keys cannot be used in the input textfield #177

Open
FelixDombek-TomTom opened this issue Mar 11, 2024 · 3 comments
Open

Dead keys cannot be used in the input textfield #177

FelixDombek-TomTom opened this issue Mar 11, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@FelixDombek-TomTom
Copy link
Contributor

In some international keyboard layouts, such as "English (US International)", some keys are "dead", for example the single/double quote key. The behaviour is usually like this: When I enter a single quote or double quote, a diacritic is inserted. Then on the next keypress, one of 3 things happens:

  • If the next char can be combined with the diacritic, this is done; - if I press space, the diacritic is transformed into the actual single or double quote; - if I enter any other char, the diacritic is unchanged and the next char is added after it.

This also works in all browser textfields. But not in Chatty.

Instead, when I enter the next char, regardless of what it is, the char is not entered, the diacritic is not changed, and the cursor jumps to the end of the input box.

So it is impossible to enter umlauts, quotes, etc.

@RijnBuve-TomTom RijnBuve-TomTom added the bug Something isn't working label Mar 11, 2024
@RijnBuve-TomTom
Copy link
Collaborator

I can't reproduce the issue (see movie). The dead keys just seem to work...

deadkeys.mp4

@FelixDombek-TomTom
Copy link
Contributor Author

Thanks for looking into it... strange! Although, you also seem to have trouble inputting normal double quotes? ... On my Ubuntu 22.04 I can't write a text like you did. But only in Chatty, here it works: ü ÿ. Maybe the devtools let me inspect what keyboard events the field reacts to, I need to have a look...

@FelixDombek-TomTom
Copy link
Contributor Author

FelixDombek-TomTom commented Mar 11, 2024

OK, it's weird. In Chrome, it works, but I usually use Firefox. In Firefox, when I set an Event Listener Breakpoint on Keyboard->compositionend, it also works! But when I don't set this breakpoint, it does not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants