In Writer there are several ways that the Sidebar Panel can be hidden or shown. One of those ways is to use the keyboard shortcut Ctrl+F5 to toggle Hide/Show. Another way is to use the Panel Hide/Show button. However, there is what I would think is anomalous behaviour if these two methods are mixed as follows: 1. Hide the Panel using the Hide/Show button. This retracts the entire Panel with exception that the Hide/Show button is still visible. 2. Now lets say you want to open the Panel again but this time you use the Ctrl+F5 keyboard shortcut to show the Panel. What actually happens is as follows: (a) The first press of Ctrl+F5 causes the Panel to fully retract i.e. the Panel Hide/Show button is retracted. (b) You think something is wrong as you wanted to show the Panel so you press Ctrl+F5 a second time and then the Panel extends outwards and is shown again (which was what you were trying to achieve at the outset). So it would seem that the Ctrl+F5 shortcut interprets a Panel hidden via the Panel Hide/Show button as being a Panel that is not in fact hidden at all. So, in that instance the first Ctrl+F5 keypress hides the Panel. I don't think things should be happening in that way. Ctrl+F5 routine should recognise when the panel has already been hidden by the Panel Hide/Show button and should show the full Panel on the first Ctrl+F5 keypress. I would regard that as 'expected behaviour'. The same 'issue' occurs in at least Calc, Draw and Impress.
I should add that I'm a relatively new user of LibreOffice and that I really don't know if LibreOffice 7.2.1.2 is the earliest version which is affected by this behaviour. (Apologies.)
In the French version, the shortcut [Alt Gr]+[2] to make a tilde (~) does not work, but opens or closes the styles pane.
Repro Arch Linux 64-bit, X11 Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 0bcce236059ae68c6dcc7bce8ceaec5d39c28f1c CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 21 February 2023
Dear Radish, 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
(In reply to QA Administrators from comment #4) > Dear Radish, > > 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 Yes, the bug still exists as originally reported above. Version: 25.2.0.3 (X86_64) / LibreOffice Community Build ID: e1cf4a87eb02d755bce1a01209907ea5ddc8f069 CPU threads: 32; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Vulkan; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded
I would add to the original report that I don't think the Panel Hide/Show Button should ever be completely hidden. When testing yourself please note that if using the Ctrl+F5 way of doing things a situation arises such that the Hide/Show Button entirely disappears — that should not be happening, ever. The Hide/Show Button should always be visible.
Ctrl+F5 is the shortcut for the "Sidebar", to open or close it (menu View). There is no shortcut to "Hide" or "Show" (as the button tooltips says) the sidebar; but, in both states, the "Sidebar" remains open (see the button color in menu View). The sidebar always opens in "Show" mode. So, if the sidebar is hidden (in "Hide" mode), you can close and open it to switch to the "Show" mode. When the sidebar is hidden, even F11 will close and F11 will open it (in the Styles deck). Not a bug for me. But an enhancement request could be to add uno commands to hide and show the sidebar. Same behavior with: Version: 6.4.7.2 (x64) Build ID: 639b8ac485750d5696d7590a72ef1b496725cfb5 CPU threads: 12; OS: Windows 10.0 Build 17763; UI render: GL; VCL: win; Locale: es-MX (es_AR); UI-Language: en-US Calc: threaded Version: 25.2.7.2 (X86_64) / LibreOffice Community Build ID: 5cbfd1ab6520636bb5f7b99185aa69bd7456825d CPU threads: 12; OS: Windows 10 X86_64 (10.0 build 17763); UI render: Skia/Vulkan; VCL: win Locale: es-MX (es_AR); UI: en-US Calc: threaded