- From: Pauan <notifications@github.com>
- Date: Tue, 30 May 2023 14:03:21 -0700
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/uievents/issues/346/1569098863@github.com>
@drwez When using the On-Screen Keyboard, Internet Explorer and Edge both send a single event. The bad behavior is [specific to Firefox / Chrome on Windows](https://github.com/rustwasm/wasm-bindgen/issues/1348#issuecomment-479213764), and unfortunately it does cause real-world problems: https://github.com/Pauan/rust-dominator/issues/10 https://github.com/rustwasm/wasm-bindgen/issues/1348 It's a widespread problem that affects many events, not just keydown/keypress/keyup. Even idiomatic events like `input` also have the same problem. Chrome and Firefox are simply buggy, they are sending invalid incorrect strings. They should be fixed so that they behave correctly and consistently. Ideally this behavior would be specified in the spec, so that way it is easier for the browsers to coordinate their behavior. I don't know what the wording should be, but the behavior should be something like "if an input character is outside of the BMP then the browser MUST NOT send multiple events (one event per surrogate pair), instead it MUST send a single event (which contains both surrogate pairs)". -- Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/346#issuecomment-1569098863 You are receiving this because you are subscribed to this thread. Message ID: <w3c/uievents/issues/346/1569098863@github.com>
Received on Tuesday, 30 May 2023 21:03:27 UTC