Created attachment 184266 [details] Screenshot of issue for GNOME dark mode and LO 7.6 Steps: 0. Use the operating system's dark mode 1. Open Writer 2. File > New > HTML document (now using the Writer/Wed editor) 3. Write a couple of words 4. View > HTML source Results: Poor choice of colours (e.g. black on dark grey, or bright blue), bad contrast makes it hard to read. Changing the Application Colours to "LibreOffice Dark" has no effect. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ad387d5b984c6666906505d25685065f710ed55d CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded and Version: 6.3.6.2 Build ID: 2196df99b074d8a661f4036fca8fa0cbfa33a497 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded Same on Windows: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9b46020c262045aed0beace4708565235c2523cc CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded LO 6.2 used to use red instead of black, which in my opinion was a little easier to read but obviously a bad choice. Aware of the argument to entirely remove Writer/Web in bug 95861 but in absence of moving forward with it, this is an accessibility issue.
Created attachment 184272 [details] defaults for Writer Web clip Win10 in dark theme confirmed Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 98f0dd5e15733ac7f1d929d06ab230b5f04121d5 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded
Dear Stéphane Guillou (stragu), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Reproduced with own master build: Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 2f5e75ed134cfd0224e03411ca9d7d81f319c91b CPU threads: 8; OS: Linux 6.8; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded