Created attachment 1832255 [details] Video showing the wrongly displayed cursor position using ibus-anthy in Google Documents I did choose component ibus, although this is likely not an ibus bug but a problem in google docs, but I wanted to report it somehow, maybe something can be done to improve this: Fedora-Workstation-Live-x86_64-35-20210829.n.0.iso installed in qemu-kvm with all current updates. firefox-93.0-2.fc35.x86_64 google-chrome-unstable-96.0.4662.6-1.x86_64 ibus-1.5.25-4.fc35.x86_64 ibus-anthy-1.5.13-1.fc35.x86_64 See the attached video. In the video I type わたしのなまえはやまだです first in gedit to show how it should work. After typing that hiragana, I type space to start conversion. The current conversion region is indicated by the cursor position and a purple background color. When the conversion to kanji is startet, at first the cursor position is at the left of the preedit and the conversion region is わたしの. I can then move the conversion region right with arrow-right and see that it moves because the blue background and the cursor position moves. Then I do the same in Google Documents (both in firefox and google-chrome, that makes no difference): - The cursor position is *always* shown at the right end of the preedit - The purple background color of the conversion region is not there One can move the conversion region around using the arrow keys, one just cannot see where the conversion region currently is the purple background is missing *and* the cursor position is *always* at the right end of the preedit. The same problem happens when trying to use ibus-typing-booster with the "inline completion" option in Google Documents. The color of the inline completion is missing *and* the cursor position is always at the end of the preedit, so one cannot see where the inline completion is and whether it has been accepted or not. In gedit in wayland, the colors don't work either, but at least the cursor position is shown correctly. When only the cursor position is shown but no color, it is not great at least somewhat usable. By carefully watching the cursor one can still see what is going on. But when the cursor positon is always at the right of preedit *and* there is no colour, this is completely unusable.
I think libreoffice uses ibus-x11 and this is caused by libreoffice.
This was a bug about google document hosted in firefox or chromium so libreoffice isn't relevant for the original bug report
Oops sorry, I tested the wrong component.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
@Mike FABIAN: I reported the issue to the upstream. Could you check that you observe the same issue? The behavior is different between GNOME Xorg and Wayland in Fedora 36. In both case, you need to export GTK_IM_MODULE=ibus The preedit segment color is not shown in GNOME Xorg but it's shown in GNOME Wayland in Fedora 36. The color is not shown in GNOME Wayland in Fedora 35.
Does it affect all Firefox edits or just google docs?
(In reply to Martin Stransky from comment #6) > Does it affect all Firefox edits or just google docs? Just google docs, for example here in the bugzilla entry fields it works fine.
(In reply to Mike FABIAN from comment #7) > (In reply to Martin Stransky from comment #6) > > Does it affect all Firefox edits or just google docs? > > Just google docs, for example here in the bugzilla entry fields it works > fine. It happens both in firefox and in google-chrome, so it might be a problem in google docs instead of a problem in the browsers. But if that is the case, I have no idea how to open a bug report against google docs.
Both in firefox and google-chrome the conversion region and cursor position of ibus-anthy are visiable in other places (bugzilla entries, URL bar, google search entry) but not in google docs.
Then it looks like a problem with google docs and not with Firefox itself.
(In reply to Martin Stransky from comment #10) > Then it looks like a problem with google docs and not with Firefox itself. I think it should be evaluated whether firefox's IM handling has an issue or firefox can provide the handling to each widget. I wonder if firefox's IM handling has an issue.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
It would be good to be handled by upstream.