My app is a React app. It contains an advanced text editor. To develop it we needed to catch the input events made on a contentEditable div to update an internal model. So we need to be aware about any change made to the editor. As the compositionend event is wrong, it generates a difference between our internal model and the current html of the page.
I'm not sure about what you mean by an "ibus app". And how composition events are "ibus specific" mechanism? They are event documented in the HTML5 W3C standard : https://w3c.github.io/uievents/#interface- compositionevent Is there something I should do in my app that would enable the correct mechanism? I'm not sure neither about your last question. What would be a desktop where ibus is not present at all? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1999207 Title: Error in dead key management of latin keyboards Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Composition events are incorrect in Ubuntu 22.04 for latin keyboard I opened an issue at Firefox [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1802989) that gives all the details, but they diagnosed a bug in ubuntu-ibus To reproduce the issue, you can go [here](https://developer.mozilla.org/en- US/docs/Web/API/Element/compositionstart_event#result) and type ^+u with a fr+latin9 keayboard configuration. Here is the conclusion on the bug report: Ubuntu-ibus commits dead key sequence with empty string first, then, sends only commit string without "composing" state. The latter behavior is a usual case for inputting non-ASCII characters like Emojis. In this case, browsers need to handle it without composition for compatibility between browsers. Therefore, we cannot represent the composed character insertion as a set of composition events. Anyway, dispatching 2 set of composition events for one dead key sequence may cause trouble in web apps. Therefore, as expected, the first composition should update the "preedit string" to the composed string and commit it simply. The bug was reproduced with installing Ubuntu 22.04 with English locale and adding "French (alt., Latin-9 only)" keyboard layout. And also reproduced with the other Western keyboard layouts which have dead keys. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1999207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
