Bug 1625224 - gnome-shell does not implement hide preedit text should be backported to f29
Summary: gnome-shell does not implement hide preedit text should be backported to f29
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 29
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-09-04 12:26 UTC by Mike FABIAN
Modified: 2018-11-21 05:32 UTC (History)
4 users (show)

Clone Of:
Last Closed: 2018-11-21 05:32:55 UTC

Attachments (Terms of Use)

Description Mike FABIAN 2018-09-04 12:26:02 UTC
When using Gnome Wayland on F29 and using a keyboard layout with dead keys, for example “English (US, intl., with dead keys)” the preëdit shown by ibus
when a dead key is pressed is hard to remove.

For example, when using “English (US, intl., with dead keys)”, typing


results in 


While the a is not yet typed, the " is shown in preëdit, i.e. underlined.
If one now types BackSpace to remove the " and the preëdit because
one changed ones mind, the preëdit does not disappear. Instead it moves left when typing more BackSpaces and right when typing spaces. Typing an a now results in the a being inserted to the left of the " in preëdit and the preëdit moves right.

I found it quite hard and not obvious to get rid of that sticky preëdit.
I switch to the Japanese input method ibus-kkc and typed some Japanese, then came back to the “English (US, intl., with dead keys)” layout. Now the preëdit was gone but I still could not type "a to get ä anymore.

Fujiwara San told me the workaround to get rid of the preëdit, 
I have to type a dead key sequence again, then the preëdit disappears and the dead key sequences work again.

This is very confusing, therefore I think it is worth backporting that fix to F29.

(The problem occurs only in Gnome Wayland, it works fine on Gnome Xorg).

Comment 1 Mike FABIAN 2018-11-21 05:32:55 UTC
This bug is fixed in current F29.

Note You need to log in before you can comment on or make changes to this bug.