The LO text widgets providw wrong values of the text surrounding the cursor wrong values under the following circumstances: using Wayland gnome-shell master (commit 33ffdd60) mutter master (commit 33ffdd60) gtk 3-24 (commit 36656ea13a735377e59376276727edf63b0e035b) libreoffice 6.1 (libreoffice 6.0 will likely crash) the issue is that the zwp_text_input_v3 protocol mandates text input *not* to include the preedit text contents, while LibreOffice includes it. This is an issue uncovered in the Gtk bug: https://gitlab.gnome.org/GNOME/gnome-shell/issues/585 Is this a problem in the LO implementation of the text field?
@Caolán, I thought you might be interested in this issue...
how do I test this exactly ? Under F29 enabling "Chinese (Intelligent Pinyin)" input engine under GNOME and typing some random letters I don't seem to trigger our signalIMRetrieveSurrounding method which is the one that calls gtk_im_context_set_surrounding. Clearly migrating to native gtk3 widgets will have solved this for the specific cases where the native widgets are used, but that's not all of them yet and there'll presumably always be some places where they won't be.
I have tested the issue using wlroots' reference compositor (rootston), together with the virtboard virtual keyboard, which can be found here: https://source.puri.sm/Librem5/virtboard I found the issue by analyzing logs produced with the WL_DEBUG=1 env variable.
Hello Dorota, A new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Dorota Czaplejewicz, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Dorota Czaplejewicz, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp