Bug 157722

Summary: Libreoffice Tabbed UI being misaligned on mac os (happens on every single libreoffice app)
Product: LibreOffice Reporter: Martin Leško <lessko37>
Component: LibreOfficeAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: stephane.guillou
Priority: medium    
Version: 7.6.2.1 release   
Hardware: ARM   
OS: macOS (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: Libreoffice misaligned UI

Description Martin Leško 2023-10-12 09:47:22 UTC
Description:
Hi, i currently use Macbook Air M2 15 inch and i've been recently trying to switch from apple's iwork (pages, keynote, numbers) office suite to Libreoffice with the Tabbed UI variant, because it's more convenient for me. However when i tried this layout, the top tabbed bar was misaligned. Tried the same ui variant on ubuntu, but without any issues.

Any solutions to this ?

Steps to Reproduce:
1. Open Libreoffice app (mac os only)
2. From the Create section on the sidebar chose one of the options of your choice
3. Go to View -> User Interface 
4. From the UI variants choose Tabbed and select Apply to All

Actual Results:
It misaligned the the tabbed bar used for switching between various options like: File, Home, Insert, Layout, References, Review, View, Extension, Tools (Happens also on other libreoffice products, this is just Libreoffice Writer example)

Expected Results:
It should apply the Tabbed UI variant without any misalignments in the User interface.


Reproducible: Always


User Profile Reset: No

Additional Info:
Libreoffice info: 

Version: 7.6.2.1 (AARCH64) / LibreOffice Community
Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333
CPU threads: 8; OS: Mac OS X 14.0; UI render: default; VCL: osx
Locale: en-US (en_SK.UTF-8); UI: en-US
Calc: threaded
Comment 1 Martin Leško 2023-10-12 09:48:55 UTC
Created attachment 190165 [details]
Libreoffice misaligned UI

The misliagnment is highlighted in red oval
Comment 2 Stéphane Guillou (stragu) 2023-10-13 22:32:58 UTC
Thanks for the report. This is already tracked in bug 127610.

*** This bug has been marked as a duplicate of bug 127610 ***