Bug 155653 - simplify the activation of dark mode
Summary: simplify the activation of dark mode
Status: RESOLVED DUPLICATE of bug 118320
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.4.7.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-02 18:42 UTC by ghosts15
Modified: 2023-06-02 19:06 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ghosts15 2023-06-02 18:42:20 UTC
Description:
You should fix and simplify the possibility of putting the application in dark mode, it is not possible that I have to change 30 options (random number but still high) to activate dark mode ,other applications already do it automatically which does not happen here.

I changed all the options but the application bar always remains white even if the OS is set to dark mode

Steps to Reproduce:
I followed a video on yotube that explained how to do it but it didn't work:https://www.youtube.com/watch?v=6fqiVlgUtJM

Actual Results:
a fake dark mode... the application bar (and not only also the settings and other menus) still remains white.



Expected Results:
A serious and functional dark mode that the ENTIRE application becomes dark mode and not just some aprti


Reproducible: Always


User Profile Reset: Yes

Additional Info:
---
Comment 1 ghosts15 2023-06-02 18:45:33 UTC
A serious and functional dark mode, in which the ENTIRE application becomes dark and not just certain parts. *
Comment 2 Mike Kaganski 2023-06-02 19:06:11 UTC
Interesting, if there will come a day when people would at least read release notes of the newer version of the old software they still use. Including automatic detection, enabled by default; and a manual switch in View options.

https://wiki.documentfoundation.org/ReleaseNotes/7.5#General_changes

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