Description: Correct selection: If I use the mouse and choose an item from the list. If I use the keyboard and choose an item from the list. Mistake: If I use the keyboard and choose an item from the list, but the mouse points to another item in the list, what the mouse points to is selected and not what the keyboard selected when using the arrows and pressing Enter. Steps to Reproduce: 1.Create a list into Data Validity 2.Use keyboard to select a item and the mouse should point another item from the list.(point where you may have left it) 3.Press Enter in keyboard Actual Results: The selected item is what the mouse was pointing to and not what the keyboard selected. Expected Results: You must select what the keyboard picks. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: 50(Build:3) CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US 7.5.0-1 Calc: threaded
I can confirm this (log-lived already) `bug but want to specify what's up in my particular case: I can not select any list member by keyboard only, I have to do that by the mouse, or first I have to select the drop-down icon by the mouse and then I can choice the list item by up/down keys. If I came to that cell by up/down/left/right keys and select the validation list by Alt+down then up & down keys has no effect and I have to use mouse. Please correct the bug as it's quite inconvenient requirement to use mouse in this situation Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 12; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: ru-RU (ru_RU.UTF-8); UI: ru-RU Flatpak Calc: threaded
Everything works fine for me with random example file, attachment 183304 [details] Please attach an example that shows the problem. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document. Version: 7.5.2.0.0+ (X86_64) / LibreOffice Community Build ID: 1e7ee035992a0b29f42eac56ad82e2a1b0fe8ccd CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: en-US (C.UTF-8); UI: en-US Calc: threaded Arch Linux 64-bit, X11 Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f51b220b953ec71fb742f799fbe645a93cf3d944 CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 29 March 2023
Dear Juan Perez, 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 Juan Perez, 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