[Expired for gnome-settings-daemon (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-sett
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://w3c.github.io/uievents/#interface-compositionevent
I'm certainly not an expert on
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 betwee
** Bug watch removed: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #682
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/682
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
http
Good. Then let me try to explain the nature of the problem you
encountered.
It's not really an ibus issue. But GNOME integrates ibus into its
desktop, and this is about the way they do so.
ibus is started and configured by default in GNOME desktops. But for
some reason they have an on/off mechani
