Description: In Writer form fields are displayed with dark background and white font when using dark mode and having the colors on standard. Exporting such a document to pdf with fillable formfields creates black text on white background (as intended) but the fields have a dark background and white font. It works, but looks rather bad and though those forms are supposed to be used without printing, a lot of people still print them out.. This also affects radiobuttons and other elements. As a workaround you can manually set the background and color of the fields in writer, but as the fontcolor is buggy, it would be great if this issue could be fixed. (If somebody finds this and needs the workaround: enter a few characters in a field so you can check on the fly. Select all fields, change the background color as desired (I use white for pdf forms). Then enter the submenu next to the font and under effects pick a color other than black, color in the example should change, now pick black) As far as I know dark mode is still experimental but I couldnt find if there is another section to track bugs, so I hope I'm in the right place. Steps to Reproduce: 1.create form in dark mode 2.export to pdf Actual Results: 3.your pdf is in white with black text, but your textfields are black with white text Expected Results: your pdf is black text on white background, including textfields, radiobuttons etc... Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 16; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded
Created attachment 183436 [details] Test pfd with form as exported without workaround
Created attachment 183437 [details] odt used to export test pdf
I believe this is a duplicate of bug 144863. Can you please confirm?
(In reply to Rafael Lima from comment #3) > I believe this is a duplicate of bug 144863. > > Can you please confirm? You are right, this is a duplicate, thanks.
*** This bug has been marked as a duplicate of bug 144863 ***