Created attachment 191844 [details] Screenshot showing input help popping up behind buttons In calc, version 7.6.4.1, if you use a combination of buttons and input help, the input help will always pop-up behind the buttons. Even if you edit each button via Tools->Forms->DesignMode, then Select button and Arrange->Send to Back. The Arrange action seems to be completely ignored on buttons in calc. However, if you enter DesignMode, then input help will display over the top of buttons. But, as a result of using DesignMode, the buttons are only selectable, not clickable to trigger an action. I first noticed this behavior in 7.6.2.1 when porting a spreadsheet to LibreOffice from excel.
I tested with LibreOffice 7.6.4.1 on macOS 13.6.3 and the input help stays on top of the button even when I am not in design mode. UI render is Skia/Raster. Please copy and paste here the contents of your LibreOffice - About by clicking the copy button. This allows us to know more about your system. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information.
Problem is occurring with macOS 14.2.1 Sorry I did not include that in original report. Requested LibreOffice information: Version: 7.6.4.1 (AARCH64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 10; OS: Mac OS X 14.2.1; UI render: Skia/Metal; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Ok, does it make a difference, if you deactivate this: LibreOffice - Preferences - LibreOffice - View - Use Skia for all rendering
No, Unchecked box "Use skia for all rendering", applied and restarted. Same result, help box pops-up behind buttons. As an experiment I enabled "Use Hardware acceleration", but box becomes unchecked after apply and restart. So, no fix there either.
Dear Ed, 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