Re: [uievents] How do web apps distinguish if a keydown event causes text input? (#18)

First, this idea doesn't take care if the key causes composition.

When "keydown" event for a printable key is dispatched, browsers computes its .key value with keyboard layout information of something:
1. When the key causes text input, just set the character(s)
2. When the key doesn't cause text input like Ctrl+C or Command+V, needs to compute what character(s) is inputted without the modifier(s). (example 28 - 30 of https://w3c.github.io/uievents/#keys-modifiers)

My idea is that there is a new attribute if the keydown event is #1 or #2. As the example in the first report, this feature must help such keyboard layout users' accessibility on complicated web apps.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/18#issuecomment-151677206