Support for composition events

[birtles]

So far as I can tell, although jsx.d.ts includes a definition for composition events such as onCompositionEnd, they are not implemented.

Furthermore, while isComposing is available through InputEvent, it is not normalized between browsers so, for example, in Firefox there will be an input event where it is true but there is not in Chrome. Without composition events it is not possible to work around this and, for example, only update search results once the current composition has been committed.

Test case:

https://codesandbox.io/s/bold-currying-vqfq8

[birtles]

Test case:

https://codesandbox.io/s/bold-currying-vqfq8

Typing and committing あ in the above test case gives:

Firefox:

input (data: あ, isComposing: true)
input (data: あ, isComposing: false)

Chrome:

input (data: あ, isComposing: true)
input (data: あ, isComposing: true)

[birtles]

For what it's worth, the browser interop issue has some discussion at:
w3c/uievents#202

It would be nice to have these events regardless of the outcome of that, however.

[marvinhagemeister]

Thanks for posting this. I've read through the linked w3c issue a couple of times, but I'm not sure what the expected behavior is. There seem to be arguments made in favor of both sides. From what I can gather so far, the firefox implementation is the preferred one. Is that correct?

[birtles]

Sorry, I possibly confused the issue by linking to that spec discussion. For what it's worth, as a Web developer, I find the Firefox behavior more useful (e.g. for ignoring uncommitted input).

As far as Preact is concerned, however, the issue is simply that authors can't rely on isComposing both due to compat issues and because the Chrome behavior makes it impossible to ignore uncommitted input. As a result authors needs to listen to composition events instead but Preact does not appear to implement them (unlike React). Instead, it seems authors need to add native event listeners to elements, e.g.: birchill/hikibiki-app@4b324e7

[developit]

Hi @birtles - I think this is actually a case sensitivity issue. My guess is that you'll find this works:

<input oncompositionend={() => { ... }} />

[birtles]

Hi @birtles - I think this is actually a case sensitivity issue. My guess is that you'll find this works:

<input oncompositionend={() => { ... }} />

Oh yes, you're right. That does indeed work.