Description: Dialog box does not respond to default OSX keyboard shortcut when attempting to select the first button in the dialog box when closing a file. This applies to all file types. Steps to Reproduce: 1. Create new file 2. hit Apple+W (Cntrl+W) to close file 3. hit Apple+D to choose the "D" in the word "Dont" Actual Results: program ignores the customer Expected Results: program should click the button for "Dont" Reproducible: Always User Profile Reset: No Additional Info: The first letter of the text string on a button is the letter that the keyboard shortcut refers to in all native OSX applications. It is expected to work here also. It does not. It is obviously quite minor. The customer can move off the keyboard to the pointing device and click the button for "Dont Save". However it would be nice if it honored the keyboard request.
I can confirm this Version: 7.2.5.2 / LibreOffice Community Build ID: 499f9727c189e6ef3471021d6132d4c694f357e5 CPU threads: 10; OS: Mac OS X 12.2; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
@Sjobeck: Can you give an example of an macOS application where this works? In Pages when pressing cmd + w to close document and then pressing cmd + d in the save dialog, nothing happens.
(In reply to steve from comment #2) > @Sjobeck: Can you give an example of an macOS application where this works? > In Pages when pressing cmd + w to close document and then pressing cmd + d > in the save dialog, nothing happens. Cmd + first letter of button label is indeed the convention on macOS in dialogs where you only have a set of buttons to choose a course of action. The dialog you mention is of a different kind. The shortcut for the “Delete“ button in such Save dialogs is Cmd + Backspace. But this is truly a minor issue because the user can just hit Tab to move focus to the “Don't Save“ button.
This also works in MSO Setting back to New
Dear Sjobeck, 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