Comment 12 for bug 1999207
Revision history for this message
| Gunnar Hjalmarsson (gunnarhj) wrote | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
On 2022-12-20 21:39, Sharcoux wrote:
> 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:/
I'm certainly not an expert on the topic. At this point I just observe. And when testing, using your test case ^+u, I only see the expected sequence of composition* events if ibus is up and running. Btw, you saw it yourself when it started to work for you on a GNOME desktop only when you had enabled an ibus input method.
I should add that also Chrome requires ibus to generate the expected sequence of composition* events; on a desktop where ibus is not present (or completely disabled) you won't see the expected sequence.
Maybe GTK itself isn't standards compliant in this respect.
> Is there something I should do in my app that would enable the
> correct mechanism?
I don't know. In the upstream issue I mentioned, there are a couple of workarounds which might help. But that would just be a replacement for enabling an ibus input method. And in case of Wayland they would be poor workarounds with adverse side effects.
> I'm not sure neither about your last question. What would be a
> desktop where ibus is not present at all?
Most non-Ubuntu desktops, actually. :) One example is Xubuntu, which I used when testing. Another option is to simply uninstall ibus on your Ubuntu desktop.