Bug 152221 - Changing macOS dark mode status partially applies on LibreOffice
Summary: Changing macOS dark mode status partially applies on LibreOffice
Status: RESOLVED DUPLICATE of bug 152184
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.5.0.0 alpha0+
Hardware: All macOS (All)
: medium trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-25 15:29 UTC by dhina
Modified: 2022-11-28 16:12 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Actual results (preference window) (75.97 KB, image/png)
2022-11-25 15:30 UTC, dhina
Details
Expected results (preference window) (83.96 KB, image/png)
2022-11-25 15:31 UTC, dhina
Details
Actual results (Writer) (62.40 KB, image/png)
2022-11-25 15:31 UTC, dhina
Details
Expected results (Writer) (47.58 KB, image/png)
2022-11-25 15:32 UTC, dhina
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dhina 2022-11-25 15:29:14 UTC
Description:
If the macOS dark/light mode is changed while LibreOffice is opened, it applies only on some part of LibreOffice.

Steps to Reproduce:
1. Open LibreOffice
2. Change macOS to dark mode

Actual Results:
Some parts are still in 'light' mode

Expected Results:
Everything should be in dark mode


Reproducible: Always


User Profile Reset: No

Additional Info:
I guess it is related to changes made to solve bug #152183

It requires to restart LibreOffice for the dark mode to fully apply.
Comment 1 dhina 2022-11-25 15:30:09 UTC
Created attachment 183781 [details]
Actual results (preference window)
Comment 2 dhina 2022-11-25 15:31:13 UTC
Created attachment 183782 [details]
Expected results (preference window)
Comment 3 dhina 2022-11-25 15:31:52 UTC
Created attachment 183783 [details]
Actual results (Writer)
Comment 4 dhina 2022-11-25 15:32:17 UTC
Created attachment 183784 [details]
Expected results (Writer)
Comment 5 V Stuart Foote 2022-11-28 16:12:25 UTC

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