Bug 152263 - The Left Bar Element Name of LibreOffice Base in macOS Dark has Dark Text on Dark Background
Summary: The Left Bar Element Name of LibreOffice Base in macOS Dark has Dark Text on ...
Status: RESOLVED DUPLICATE of bug 152253
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
7.5.0.0 alpha0+
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: macOS-Dark-Mode
  Show dependency tree / graph
 
Reported: 2022-11-28 10:18 UTC by Rizal Muttaqin
Modified: 2022-12-07 10:53 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Unselected element in left side of Base has dark text on dark background (306.46 KB, image/jpeg)
2022-11-28 10:18 UTC, Rizal Muttaqin 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rizal Muttaqin 2022-11-28 10:18:06 UTC 
Created attachment 183851 [details]
Unselected element in left side of Base has dark text on dark background

Description:
Unselected element name in left side of LibreOffice Base has dark text on dark background. 

Steps to Reproduce:
Open a Base file

Actual Results:
dark text in element name

Expected Results:
light text in element name


Reproducible: Always


User Profile Reset: No

Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 3b0b9fcb80242abcedc01eb388a57b1016916353
CPU threads: 4; OS: Mac OS X 13.0.1; UI render: Skia/Raster; VCL: osx
Locale: en-US (en.UTF-8); UI: en-US
Calc: threaded
Comment 1 Sierk Bornemann 2022-11-28 15:50:18 UTC 
I can confirm the issue in question.


Version: 7.5.0.0.alpha1+ (AARCH64) / LibreOffice Community
Build ID: e76b1faa3326e5cffed4472fcd410b5abf273067
CPU threads: 10; OS: Mac OS X 13.0.1; UI render: Skia/Metal; VCL: osx
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded
Comment 2 Caolán McNamara 2022-12-07 10:53:17 UTC 

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