Description: Why it's wrong: The <RCtrl> + <Menu> combination can be used in Linux to switch to a second keyboard layout. Expected Behavior: <Menu> opens a context menu, <RCtrl> + <Menu> (if configured) selects an alternate keyboard layout. Actual behavior: <Menu> opens a context menu, <RCtrl> + <Menu> (if configured) selects an alternate keyboard layout AND the application opens a context menu. Steps to Reproduce: press <RCtrl> + <Menu> while editing a document or table (to switch to the second keyboard layout) Actual Results: a context menu appeared Expected Results: a context menu does not open Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Version: 7.2.0.4 / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 12; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: ru-RU (ru_RU.UTF-8); UI: ru-RU Calc: threaded
This depends much on the desktop environment and configuration. KDE's default shortcut to switch to the next keyboard layout is ctrl+alt+K. Meaning we cannot guarantee that shortcuts work in all environments. Looking into the code it seems we handle KEY_MENU / KEY_CONTEXTMENU but not in combination with other keys. Don't see how we can solve the problem.
I think it would be reasonable to open the context menu in reaction on <Menu> only if modifiers are not pressed (in Firefox <Menu> triggers the context menu only alone or with Shift but not with Ctrl nor Alt, although e.g. KDE's KWrite triggers it always).
Dear Danila Ikryannikov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug