- From: Gary Kacmarcik <notifications@github.com>
- Date: Tue, 27 Jun 2023 14:51:56 -0700
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 27 June 2023 21:52:01 UTC
> The standard currently refers to using composition events, but they are not a replacement as they only give you the current composed state, not the symbol that was just included to update the state. The `data` attribute of the `compositionupdate` event should indicate the dead key. As shown in this example: https://www.w3.org/TR/uievents/#example-a785f64b > Composition events also only work on input fields, not other keyboard event targets such as a canvas. So even if they did contain the proper information, they would still not be a valid replacement. You should be able to get these events if you give the canvas a `tabindex` attribute. I realize this isn't ideal for your case, but I hope that this is enough to unblock you. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/343#issuecomment-1610267582 You are receiving this because you are subscribed to this thread. Message ID: <w3c/uievents/issues/343/1610267582@github.com>
Received on Tuesday, 27 June 2023 21:52:01 UTC