Created attachment 184574 [details] Default color for buttons and borders in forms to dark Open the attached screenshot. In LO 7.5.0.1 buttons and border round a form field switched from light grey to dark grey. This shouldn't happen, because contrast from characters and background will be to low. Test it also with the attached database. Open the form. LO version: Version: 7.5.0.1 (X86_64) / LibreOffice Community Build ID: 77cd3d7ad4445740a0c6cf977992dafd8ebad8df CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded
Created attachment 184575 [details] Open form in database. Don't need macros enabled. See dark gray buttons.
This was changed in ea36e0502c0bc381577cfa1b1a7fedf0f05d1d72 Let's ask UX what they think and if they want to implement a change.
Bug 150786 explains why it was done. Caolan, can we apply the non-native look only on export to PDF? Or provide an option to switch it on/off. Meanwhile you can set the background and foreground color to any value.
The results in the screenshot don’t fail neither WCAG AA nor WCAG AAA, so this doesn’t seem to be a significant a11y issue
As I understand bug 150786 it is has been changed also for LO 7.4.3. But: In LO 7.4.6.2 the form controls will get the "normal" color (buttons and borders), in Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded it will be changed to dark gray. Why should an export for form controls to *.pdf destroy the design of older forms?
The application dark mode makes the document not WYSIWYG anymore. For the buttons it's even more complex as your theme might be dark (and buttons are dark with white font) but when exported to PDF those colors are not taken into the document (neither you can be sure the document is drawn identically on someone else's machine and explicitly setting the font color to white would be wrong). I see two solutions: a) apply some default, hard-coded colors on export (and show it locally depending on the used theme), b) always use non-native colors but make it editable (meaning effectively to bind it to some application color), and c) just WF/NAB the issue. Essentially the point is how PDF handles forms with the goal to have a button blend into the system look and feel; guess that's defined in PDF and we just need to properly export. => new, needsdevadvice