Description: Spinboxes not themed in Dark-Mode Steps to Reproduce: 1. Open Writer (in Dark-Mode) 2. Format -> Page Style -> Transparency tab (doesn't really matter) Actual Results: The spinboxes stick out being as not being themed Expected Results: Dark spinboxes Reproducible: Always User Profile Reset: No Additional Info: Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bd339e1937d12cf7f62276e537bca96e01ef8ae4 CPU threads: 4; OS: Windows 10 X86_64 (build 19045); UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded
Created attachment 201769 [details] TB78 nightly 2025-07-12 Win11 os/DE 'Dark' color sense, spin boxes are themed Can not confirm. Parallel /a install of TB78 WIX based nightly of master, Win11 in 'Dark' sense. LO Appearance theme has not been enabled. LO spin boxes pick up reasonable fg/bg colors from os/DE. Likewise if the Win11 color sense is changed to 'Light'. Reasonable 'Automatic' colors from os/DE are applied on toggle. Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e38d4e8cf2b1a1b5c146acbe325d31f84da676b0 CPU threads: 28; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
Created attachment 201773 [details] Screenshot
Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b99f595b47d1a60e6af6ba742665a92803b7c68b CPU threads: 4; OS: Windows 10 X86_64 (build 19045); UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: nl-NL Calc: CL threaded
Still the same issue, tried an profile reset. No change. Attachment 201769 [details] shows indeed what I would expect So Win10 specific?
(In reply to Telesto from comment #4) > Still the same issue, tried an profile reset. No change. Attachment 201769 [details] > [details] shows indeed what I would expect > > So Win10 specific? Could it be the same topic as bug 170048?
(In reply to Buovjaga from comment #5) > (In reply to Telesto from comment #4) > > Still the same issue, tried an profile reset. No change. Attachment 201769 [details] > > [details] shows indeed what I would expect > > > > So Win10 specific? > > Could it be the same topic as bug 170048? Possibly. I didn't read the discussion in detail, but it appears to be about Windows 10 < 20H1. My issue is with 22H2 However, I don't expect someone looking into this bug before Windows 10 hitting End-Of-Life [for the consumer market]. So in that sense it might be closed
(In reply to Telesto from comment #6) > However, I don't expect someone looking into this bug before Windows 10 > hitting End-Of-Life [for the consumer market]. So in that sense it might be > closed Well, support for Win 7 was only removed in 25.8, so if that is anything to go by we might support Win 10 still in the year 2031...