Re: [w3c/uievents] Dead keys and unsupported base characters (#120)

I'm not sure I follow the example 27. It looks as if in the end, nothing is returned. 

On Windows (for example with the standard German keyboard), when I type a dead key for the acute accent followed by a character not supported (q), I get a spacing accent followed by the letter ( ´q ) as an indication that something didn't go as planned. (That two character sequence is echoed on keyup for q).

It would be strange if it worked one way in some applications and not others.

I'm not sure what other keyboard layouts do (e.g. those supporting diacritics for which there isn't a spacing clone). The upshot is that it looks like it's not a universal behavior and in cases where users have installed a particular keyboard, the expectation would seem that that selection drives the policy.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/120#issuecomment-628875687