Bug 161286 - Qt VCL does not send input method cursor rectangle based on preedit cursor
Summary: Qt VCL does not send input method cursor rectangle based on preedit cursor
Status: RESOLVED DUPLICATE of bug 160838
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
24.2.3.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-27 04:11 UTC by Xuetian Weng
Modified: 2024-05-27 13:55 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Qt6 plugin, the reported cursor is at the beginning of preedit (59.58 KB, image/png)
2024-05-27 04:11 UTC, Xuetian Weng
Details
Gtk3 plugin, which works as expected. (58.08 KB, image/png)
2024-05-27 04:12 UTC, Xuetian Weng
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Xuetian Weng 2024-05-27 04:11:36 UTC
Created attachment 194364 [details]
Qt6 plugin, the reported cursor is at the beginning of preedit

When using Qt 6 plugin, the cursor rectangle (Qt::ImCursorRectangle) reported by libreoffice is at the beginning of preedit, not at the cursor of preedit.

Comparing to Gtk3, the position is reported correctly.

For example, if the preedit is like "あゝ|ああ"  ( "|" means the position at the cursor), the Qt6 plugin will report cursor rectangle at the very beginning, while Gtk3 plugin will report the position  at cursor "|".

Can be easily reproduced with mozc or anthy (with either ibus, or fcitx5). With default configuration of mozc/anthy, press "a", "a", "a", "a", space, left, space, will reproduce the issue.

See the screen shot for more details.
Comment 1 Xuetian Weng 2024-05-27 04:12:39 UTC
Created attachment 194365 [details]
Gtk3 plugin, which works as expected.

Gtk3 screenshot, works properly.
Comment 2 Stéphane Guillou (stragu) 2024-05-27 13:55:29 UTC
Thank you for the report!
I think this is the same issue as already tracked in bug 160838.
Michael, correct me if I'm wrong.

*** This bug has been marked as a duplicate of bug 160838 ***