Description: I really like the "grouped bar compact mode" as the top bar changes depending on the context which makes it very easy to find a setting. By default the top bar will be in text mode and show text related options like text size, fonts, colours, etc, and after selecting an image it will change to image mode. But when I select text and the top bar changes back to text mode a part of the top bar isn't shown (I will add an attachment after filing this bug). This happens in Writer, but not in Impress, I haven't verified reproducibility in Calc or other LibreOffice apps. Steps to Reproduce: 1. Set UI to "grouped bar compact" mode, the top bar will change depending on the context. 2. Select an image to change the top bar to image mode 3. Place the cursor in a text field to change it back to text mode Actual Results: The lower row of the top bar will disappear and I have to click a button or text field in the upper row to bring it back. Expected Results: Show both the upper part and the lower part Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Information from Help - About LibreOffice: Version: 7.3.0.3 / LibreOffice Community Build ID: 30(Build:3) CPU threads: 8; OS: Linux 5.16; UI render: default; VCL: kf5 (cairo+xcb) Locale: nl-NL (nl_NL.UTF-8); UI: en-US 7.3.0-4 Calc: threaded My OS and stuff: Operating System: Arch Linux KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.7-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-10300H CPU @ 2.50GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics
Created attachment 178163 [details] A video showing the problem
I can repro in 7.3, but not with the latest, so closing. Arch Linux 64-bit, X11 Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a365b4850299778992350c690b064728be6b74ef CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Jumbo Built on 15 December 2022
*** Bug 148144 has been marked as a duplicate of this bug. ***